mirror of https://github.com/nocodb/nocodb
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2.5 KiB
2.5 KiB
title | description | tags | keywords |
---|---|---|---|
Okta | Learn how to configure Okta as an identity provider for NocoDB. | [SSO Okta SAML] | [SSO Okta SAML Authentication Identity Provider] |
This article briefs about the steps to configure Okta as Identity service provider for NocoDB
NocoDB, Retrieve SAML SSO
Configuration details
- Go to
Account Settings
- Select
Authentication (SSO)
- Click on
New Provider
button - On the Popup modal, Specify a
Display name
for the provider; note that, this name will be used to display the provider on the login page - Retrieve
Redirect URL
&Audience / Entity ID
; these information will be required to be configured later with the Identity Provider
Okta, Configure NocoDB as an Application
- Sign in to your Okta account
- Navigate to
Applications
>Applications
- Click
Create App Integration
- Navigate to
- In the pop-up with title
Create a new app integration
chooseSAML 2.0
as the Sign-in method - On the
Create SAML Integration
page, in the General settings - provide a name for your app; clickNext
- In the
Configure SAML
section:- Enter the
Redirect URL
copied from NocoDB in theSingle sign-on URL
field. - Add the
Audience URI
copied from NocoDB in theAudience URI (SP Entity ID)
field. - Choose
Email Address
from theName ID format
options. - Select
Email
from theApplication user-name
options. - Click
Next
- Enter the
- Complete any additional information in the final step and click
Finish
- On your application's homepage,
- Navigate to the
Sign-on
tab - Copy the
Metadata URL
from theSAML 2.0
section
- Navigate to the
- Go to the
Assignments
tab and clickAssign
to assign people or groups to this application.
NocoDB, Configure Okta as an Identity Provider
- Go to
Account Settings
>Authentication (SSO)
>SAML
- On the "Register SAML Identity Provider" modal, insert
Metadata URL
retrieved in step above; alternatively you can configure XML directly as well Save
For Sign-in's, user should be able to now see Sign in with <SSO>
option.
:::note
Post sign-out, refresh page (for the first time) if you do not see Sign in with <SSO>
option
:::