mirror of
https://github.com/nocodb/nocodb.git
synced 2026-04-30 22:36:49 +00:00
3.2 KiB
3.2 KiB
title, description, tags, keywords
| title | description | tags | keywords | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Azure AD (Entra) | Learn how to configure Active Directory as an identity provider for NocoDB. |
|
|
:::info For SSO Access - please reach out to sales team. :::
This article briefs about the steps to configure Active Directory as Identity service provider for NocoDB
NocoDB, Retrieve SAML SSO Configuration details
- Go to
Account Settings - Select
Authentication (SSO) - Click on
New Providerbutton - On the Popup modal, Specify a
Display namefor 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
Azure AD, Configure NocoDB as an Application
- Sign in to your Azure account and navigate to
Microsoft Entra admin center>Identity>Enterprise applications - Click
+ New application - On the
Browse Microsoft Entra Gallerypage, selectCreate your own applicationfrom the navigation bar. a. Provide your application's name. b. ChooseIntegrate any other application you don't find in the gallery (Non-gallery)c.Create - On your application page, navigate to
Manage>Single sign-on>SAML - Go to the
Basic SAML Configurationsection underSet up Single Sign-On with SAMLand clickEdita. Add theAudience URIunderIdentifier (Entity ID). b. Add theRedirect URLunderReplay URL (Assertion Consumer Service URL). c. ClickSave - In the
Attributes & Claimssection, clickEdita. Edit the "Unique User Identifier (Name ID)" claim: - SelectEmail addressfrom theName identifier formatdropdown - ChooseAttributeas theSource- In theSource attribute, selectuser.mail- ClickSave[//]: # ( b. (Optional) For custom claims:) [//]: # ( - Click Add new claim, provide details, and save.) [//]: # ( - Ensure the claim is visible in the Additional claims section.) [//]: # ( - Copy the claim name for later use in NocoDB SAML configurations.) - Go to the
SAML Certificatessection and copy theApp Federation Metadata URL - on the Application's Overview page,
- Click
Users and groups, - Add the necessary users or groups to the application.
- Click
NocoDB, Configure Azure AD as an Identity Provider
- Go to
Account Settings>Authentication>SAML - Insert
Metadata URLretrieved 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
:::




