Set up social login

We provide the capability within authentication journeys/trees to support trusted Identity Providers (IdP), like Apple, Facebook, Google, and many others, for authentication and identity verification on behalf of ForgeRock. This is often referred to as social login or social authentication. These IdPs return the necessary user information to your server.

Depending on the device platform—​Android, iOS, or web—​the user is either redirected from the current web application, or the login page to the IdP’s authorization server, or, if on a native mobile app, the user is directed to the IdP’s authentication SDK, if available. Once on the IdP through a web page or the SDK, the user authenticates, and provides the necessary consent required for sharing the information with ForgeRock. When complete, the user is redirected back to your app or to the server to complete the authentication journey.

It’s common to offer these social login options in addition to traditional authentication with username and password, but they can be used alone.

A screen capture of a login page with a common combination of methods:

Before implementing social login, read Limitations.

This how-to covers setting up an PingOne Advanced Identity Cloud tenant with the IdPs that the SDKs support: Apple, Facebook, and Google.

PingOne Advanced Identity Cloud supports additional IdPs.