Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
In this section you will learn about Okta SSO
SSO button should appear automatically on the login and register pages when visiting Jet Admin from your custom domain.
In this section you will learn how to build Sign In/Sign Up Page
You don't need to build the Sign-in/Sign-up page in the UI, as Jet already has a separate Sign-in/Sign-up page builder.
To access it,
Click on the Sign-in & Sign-up icon inside the builder
Sign-in/Sign-up page has three major sections:
(1) Menu - configure the appearance, sign-in, and sign-up separately
(2) The preview - check in real-time changes taking effect
(3) Setting - this is where the configuring happens
To be able to customize the Sign-in/Sign-up, you need to set up a custom domain first. See the image below.
Learn how to set up a custom domain in the following article:
The appearance tab allows you to:
(1) Switch between the layouts
(2) Set the background picture
(3) Set the color theme
The sign-in and sign-up tabs allow you to configure the settings, specific to the sign-in and sign-up, such as Terms of service URL, titles, and customer sign-up flow for the Portal.
In this section you will learn about API calls with SSO token
When user is logged in with SSO it is possible to use SSO access token in HTTP queries (Rest API or GraphQL). Such requests are going through api.jetadmin.io endpoint or self-hosted Jet Bridge (when set up as ).
You can insert any SSO tokens in HTTP/GraphQL queries using SSO credentials section.


Choose Provider Auth0OAuth2 on Jet Admin and then copy Domain, Client ID, Client Secret from Auth0. You should also set Scope as openid,profile,email,offline_access.
Copy the REDIRECT URL from Jet Admin in the Application parameters section to Auth0 Allowed Callback URLs and click Save on both - Auth0 and Jet Admin.
SSO button should appear automatically on the login and register pages when visiting Jet Admin from your custom domain.
In this section you will learn about Auth0 SSO SAML2
SSO button should appear automatically on the login and register pages when visiting Jet Admin from your custom domain.

{
"mappings": {
"email": "Email",
"given_name": "FirstName",
"family_name": "LastName"
}
}









Step-by-step guide to authentication with Google OAuth 2.0
If you want to use Google services such as Google Sheets, Google Drive, Google Cloud and many others, this step-by-step guide can help you with Google OAuth 2.0 authentication.
Once you have created the project and selected the Rest API resource, you also selected the OAuth 2.0 authentication method - you need to select a provider.
Visit the to obtain OAuth 2.0 credentials such as a Client ID and Client secret that are known to both Google and Jet Admin.
Specify Project name and Location then click the Create button.
In the control panel, enable the API and Services you plan to use.
The API library looks like this. You can choose any service you are plan to use, but we will go through the Google Sheet API.
Once you have selected the API and services, click the Enable button.
To use this API, you need credentials. Go to the credentials menu to get started.
Сonfigure the OAuth consent screen:
Choose how you want to configure and register your app, including your target users. You can only associate one app with your project. Then click Create.
Specify the application name, scroll down the page, and click Save.
Go to the credentials menu and click Create credentials. Then select OAuth Client ID.
Then you need to select the application type. In the drop-down list, select Web application. Specify name, you also can add OAuth Redirect URL, then click Create.
https://api-dev.jetadmin.io/api/create_oauth_token_complete/
Congratulations, your client ID and client secret created.
To complete the process of adding a resource, we need to fill in the scopes field.
You can find the necessary information . For our case, the scopes look like this.
Congratulations! Now you are ready to authenticate with Google OAuth 2.0. If you still have any questions, please contact us for help.
In this section you will learn about Google SSO SAML2
Setting up SSO for your Jet Admin project requires your to set up Custom Domain for your project first.
G Suite Apps page is located at
Specify Entity ID and upload saved Metadata (.xml) file from the previous step. Entity ID should be unique text identifier of your application
ACS URL displayed at the bottom of page will be needed on the next step.
Specify ACS URL and Entity ID entered on the previous step
You should specify 3 attributes to map on Jet Admin user account:
Email should map to Basic Information - Primary Email
FirstName should map to Basic Information - First Name
LastName should map to Basic Information - Last Name
SSO button should appear automatically on the login and register pages when visiting Jet Admin from your custom domain.










Scopes
Description
https://www.googleapis.com/auth/spreadsheets
See, edit, create, and delete your spreadsheets in Google Drive
https://www.googleapis.com/auth/spreadsheets.readonly
View your Google Spreadsheets
In this section you will learn about 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.
The process is not automatic:
First you need to implement OAuth2 flow on your side and make sure it works. You should implement three types of requests for it listed below.
Any SSO integrations require you to connect your custom domain.
Contact our tech engineers to test and finish integration on our side. OAuth implementation can vary from provider to provider so we implemented ability to customize OAuth requests used in integration (HTTP method, JSON/Form data, Scope separator, etc.). Our engineers will adapt to your implementation during integration process, but we recommend to stick to the most popular industry implementations (preferable to use open source implementations for your tech stack).
These are global parameters generated on 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)
SCOPE - (optional) If your backend requires access_token to have list of scopes to make queries this parameter will be used to obtain access_token
GET https://YOUR_SSO_DOMAIN/authorize
After Sign In process user will be redirected back to Jet Admin side.
GET https://api.jetadmin.io/complete/custom_oauth_2/
POST https://YOUR_SSO_DOMAIN/token
access_token JWT payload should have fields:
first_name
last_name (optional)
username (can be equal to email)
access token and refresh token obtained on this step are saved on api.jetadmin.io side.
Can be the same as Access token URL, but with different data
POST https://YOUR_SSO_DOMAIN/token








scope*
String
ex. "openid profile offline_access" Depends on your implementation, should be minimal scope needed to get user profile (first name, last name, email)
authuser
String
0
redirect_uri*
String
https://api.jetadmin.io/complete/custom_oauth_2/
client_id*
String
CLIENT_ID
state*
String
Special OAuth2 generated code, created on Jet Admin side
redirect_uri*
String
ex. https://api.jetadmin.io/complete/custom_oauth_2/ Should be as specified here, you can validate it on your side (optionally)
response_type*
String
code
state*
String
Special OAuth2 generated code, created on Jet Admin side
code*
String
Special OAuth2 generated code, created on Custom provider side
scope*
String
Previously received scope
prompt*
String
consent
grant_type*
String
authorization_code
code*
String
Special OAuth2 generated code, created on Custom provider side
client_id
String
CLIENT_ID
client_secret*
String
CLIENT_SECRET
grant_type*
String
refresh_token
refresh_token*
String
client_id
String
CLIENT_ID
client_secret*
String
CLIENT_SECRET
{
'token_type': 'Bearer',
'access_token': 'ya29.A0ARrdaM9Hc_Hz__EhytWaIlHcYGkaszuxgKVqeEWBfErtEbHOPRF2_YtvlSY5qbkW2ZKbvbCNPtxGJJHutBsWd2hfmE8ZCdRX0bpQw5iwDfTBJZjQ7S9kKRiiCR165DyLs8hnERkjd3Z8-1-hPSt1X9MrY8aX',
'expires_in': 3599,
'refresh_token': '1//09uFin2WWZE9gCgYIARAAGAkSNwF-L9Irrrh5VtbNA35jfyWv8xnrj-VSqMKwCP-yjKtP6h6IDA6A0-S-LgqGve9Z-RLZzFdZpaE',
'scope': 'openid profile offline_access'
}{
'token_type': 'Bearer',
'access_token': 'ya29.A0ARrdaM9Hc_Hz__EhytWaIlHcYGkaszuxgKVqeEWBfErtEbHOPRF2_YtvlSY5qbkW2ZKbvbCNPtxGJJHutBsWd2hfmE8ZCdRX0bpQw5iwDfTBJZjQ7S9kKRiiCR165DyLs8hnERkjd3Z8-1-hPSt1X9MrY8aX',
'expires_in': 3599,
'refresh_token': '1//09uFin2WWZE9gCgYIARAAGAkSNwF-L9Irrrh5VtbNA35jfyWv8xnrj-VSqMKwCP-yjKtP6h6IDA6A0-S-LgqGve9Z-RLZzFdZpaE',
'scope': 'openid profile offline_access'
}























In this section you will learn about Azure AD SSO OAuth 2.0
Specify Name and New members team for newly created External SSO
In Redirect URI (optional) section fill the following fields
Platform: Web
URL: copy REDIRECT URL from Jet Admin -> External SSO -> Application parameters section.
Copy Application (client) ID and Directory (tenant) ID from App Registration page in Azure portal to Jet Admin External SSO
Then open Certificates & secrets page, create new Client secret and copy it's Value to Jet Admin Client Secret
You should also set Scope to openid,profile,email,offline_access
SSO button should appear automatically on the login and register pages when visiting Jet Admin from your custom domain.







