Social Login #

After implementing social login, they reported a 68% increase in user engagement because they were able to understand and interact with their users. – Rakesh Soni

Passkeys and Social Login #

The AppKey authentication service is built around a synced Passkey system that adheres to the FIDO2 protocol. PassKeys are a natural, more secure replacement for email/password setups, saving time and boosting productivity. With PassKeys, there’s no need for SMS- or email-based two-factor authentication, nor are there the usual risks associated with reused or easily guessed passwords. But what about social login?

Social login allows users to log in through trusted third parties like Apple, Google, or Facebook, which manage credentials securely on their end. In the email/password era, social login offered a simple way to avoid storing user credentials on separate, potentially vulnerable servers and allowed new users to onboard with minimal effort. Studies show that social login can significantly increase user engagement, especially in B2C applications.

It might seem that PassKeys could make social login obsolete. But in reality, we see social login systems adapting to the new Passkey model. As these third-party providers incorporate PassKeys, they’ll remain just as productive and secure, keeping their role in the Passkey-enabled ecosystem.

This is why AppKey chose early on to support social login in its authentication system. Social login is fully integrated into the AppKey REST API, so it delivers the same access tokens and JWT login tokens as a standard Passkey login. This approach makes it easy for developers to continue supporting social logins as they transition to PassKeys.

Preparing App for Social Login #

Currently, the AppKey service supports social logins through Apple and Google. Looking ahead, we plan to add support for Facebook, LinkedIn, Microsoft, and GitHub. To enable social login for an AppKey app, developers simply need to select the relevant options under the Options tab in the AppKey portal.

The developer must enter the Apple App Bundle ID to enable Apple Login and the Google Client ID for Google Login. Note: Social Login functions only in release mode. Social Login is not enabled by default.

Allow Apple Login #

Beyond FIDO2 passkey authentication, the AppKey authentication system also supports Apple Id Sign In. This feature streamlines the onboarding process for iOS applications, minimizing user sign-up hurdles. This functionality is fully integrated into the AppKey authentication REST API (similar to anonymous login), offering a unified JWT interface for this social login feature.

Should a developer choose to enable Apple Login, they will need to supply the Apple Bundle ID for the iOS Application. If the application needs to support both login from an iOS device and a web page, the developer may need to provide a list of Apple Bundle IDs that are comma seperated.

Note: Apple Id Sign In is operational only in release mode, and not in development mode.

Allow Google Login #

AppKey also facilitates the Google Login social protocol. This is akin to Apple Id Sign In but utilizes a GMAIL account rather than an Apple Id. You can find a comprehensive description of the Google Authentication protocol here. To activate Google Login within the client application, the developer must furnish the Google Client ID for the application. Like the Apple Bundle ID, AppKey supports multiple Google Client IDs that are comma seperated.

Just like Apple Id Sign In, the Google Login social protocol operates solely in release mode, not in development mode.