Search…
Custom SSO OAuth 2.0
Apart from a number of pre-built SSO providers we support integrating with fully Custom OAuth 2.0 compatible providers. You should implement three types for requests for it.
These are global parameters generated in your side
- CLIENT_ID - You apps client id used to identify Jet Admin requests (passed public)
- CLIENT_SECRET - You apps client secret used by Jet Admin to perform requests (stored internally)
1. Authorization URL
get
https://YOUR_SSO_DOMAIN
/authorize
Initial page which user is redirected to Sign In
get
https://api.jetadmin.io
/complete/custom_oauth_2/
After Sign In process user should be redirected here
2. Access token URL
post
https://YOUR_SSO_DOMAIN
/token
The method is called by Jet Admin backend to get Access and Refresh tokens
access_token JWT payload should have fields:
- first_name
- last_name (optional)
- username (can be equal to email)
- email
3. Refresh token URL
Can be the same as Access token URL, but with different data
post
https://YOUR_SSO_DOMAIN
/token
The method is called by Jet Admin backend to refresh expired Access token
Last modified 2mo ago
Export as PDF
Copy link
Contents
1. Authorization URL
get
Initial page which user is redirected to Sign In
get
After Sign In process user should be redirected here
2. Access token URL
post
The method is called by Jet Admin backend to get Access and Refresh tokens
3. Refresh token URL
post
The method is called by Jet Admin backend to refresh expired Access token