Authentication Federation

Authentication Federation with Google, Facebook, Twitter, and OpenID involves leveraging these platforms as identity providers (IdPs) to enable users to access multiple services using their credentials from these providers.

When a user tries to access a BlinkLink video engagement service that requires authentication federation, instead of creating a separate account, they can choose to authenticate using their existing Google, Facebook, Twitter, or OpenID credentials.

The process involves the following steps:

1. User initiates authentication: The user selects the option to sign in using their Google, Facebook, Twitter, or OpenID account.

2. User redirected to IdP: The user is redirected to the respective IdP's authentication page.

3. User authentication: The user provides their login credentials (username/password) on the IdP's authentication page.

4. IdP generates a token: Upon successful authentication, the IdP generates a security token or assertion.

5. Token sent to BlinkLink: The token is sent back to BlinkLink identity federation

6. BlinkLink identity federation validates the token: The BlinkLink identity federation service verifies the token's authenticity and checks if it corresponds to a valid user.

7. User granted access: If the token is valid, the BlinkLink identity federation grants the user access to the requested service.

By using authentication federation with these IdPs, users can enjoy a streamlined authentication experience across video engagement services without the need to remember multiple sets of credentials. Currently supported IdPs are as below:

• Google

• Facebook

• Twitter

• Apple

• OpenID