Social Login (OAuth) with Backend SDKs
This guide is meant for developers that are NOT using Descope on the frontend to design login screens and authentication methods.
If you'd like to use Descope Flows, Quick Start should be your starting point. If you'd like to use our Client SDKs, refer to our Client SDK docs.
To get started with authentication using Social Login (OAuth), refer to our Social Login Documentation. Continue reading to learn how to integrate Social Login into your application using our Backend SDKs.
Backend SDK
Install SDK
Import and initialize SDK
Start OAuth
To initiate the OAuth process, call the OAuth initiation function after the user clicks the social login button. This function returns a pre-formatted URL that the client can use to redirect the user and begin the login flow with the selected Identity Provider (e.g., Google, Facebook, Microsoft).
Finish OAuth (Exchange Token)
After the user authenticates with the OAuth provider, they will be redirected to the redirect_url
you specified.
However, to complete the login process with Descope, you'll need to extract the code from the URL and perform the token exchange which will complete the OAuth flow:
Session Validation
The final step of completing the authentication with Descope is to validate the user session. Descope provides rich session management capabilities, including configurable session timeouts and logout functions. You can find the details and sample code for backend session validation here.
Checkpoint
Your application is now integrated with Descope. Please test with sign-up or sign-in use case.