With Apple sign in, there’s the implicit assumption that you'll navigate away from your page to Apple's auth page. This flow runs counter to the way SPAs work. The user completes the sign up flow for your site. Your app navigates to Apple’s Auth page with some metadata about what information your app needs and where it should redirect the user to when it’s done.Īpple sends a FORM_POST request to the redirect url specified. User clicks the “Sign In with Apple” button. Anatomy of Sign In with Appleīasically, this is the flow of doing sign in with Apple: Let’s dive into the anatomy of the Apple Sign In flow and see why it makes things tricky.

In this post, we’ll only cover the process of adding Sign In with Apple to an Angular web app. Obviously, if you offer Apple sign in on your iOS app, you’ll need to allow Sign In with Apple everywhere. Surely adding one more third party auth provider can't be that much more work, right? Wrong! You added Google sign in to your system without too much trouble. You've added Google sign in to reduce friction on your sign up flow, and now Apple comes along and wants a piece of that third-party-sign-in pie so is holding your app hostage until and unless you integrate with their sign in system. Now all you need to do is get it through the Apple app store review. The Android App has gone through the Google Play Store review process without a hitch. You’re ready to upload the native apps to the app stores. You’ve got an Angular web app and a native counterpart. My guide doesn’t go into any detail about that but see this guide for how to set all that up. Note: There are several administrative steps that are required to integrate with Sign In with Apple that you need to configure in the App Connect Console.

Pinterest sign in with apple