On the site, it is possible to connect user registration and authentication functionality using third-party applications:
- Amazon
- X (Twitter)
Our system already contains our integrations and our accounts, and you can quickly connect them to the site, but it is also possible to connect a client account so that all registrations go through this account.
To do this, you need to register these accounts on the selected application, after which the received ID (keys) can be connected to the site. Each application has its own steps and instructions that must be implemented in order to obtain the necessary access keys in the end.
Documentation "Using OAuth 2.0 to access Google APIs" - https://developers.google.com/identity/protocols/oauth2
Brief description of steps:
- Create “OAuth 2.0 client ID” in Google API Console
- Set up the consent screen - https://cloud.google.com/sap/docs/abap-sdk/on-premises-or-any-cloud/latest/authentication-oauth-client-credentials
- In the web application, redirect the user to the Google authorization endpoint, get the “authorization code”
- The server exchanges the code for an “access token” (and possibly a “refresh token”). Google for Developers
- Use a token to access user data (for example, profile, email).
- Validate the token, protect it, manage expiration date, etc.
Official documentation for "Facebook Login" - https://developers.facebook.com/docs/development#register
*
Brief description of steps:*
- Go to "Facebook for Developers", create an application, get an "App ID" and "App Secret" - https://developers.facebook.com/docs/facebook-login/
- Configure redirect URLs, allowed domains, user permissions (“email”, “public_profile”, etc.).
- The user agrees, Facebook redirects with a code/token.
- Change the code to a token and get user data.
- Integrate with authentication/session system.
Was the article helpful?
Yes, thank you! Unfortunately no