Set Up Capella SSO Using Microsoft Entra ID
- Capella Operational
- how-to
Configure Single Sign-On (SSO) between Microsoft Entra ID and Couchbase Capella to allow your organization’s users to authenticate securely without managing separate credentials. This integration enables streamlined access management while maintaining enterprise-grade security.
Prerequisites
To configure Microsoft Entra ID as an IdP, you need:
-
To enable SSO for your Capella organization.
-
An Azure subscription with Microsoft Entra ID. For more information, see Microsoft.
-
An Entra ID tenant associated with your Azure subscription. For more information, see the Microsoft Entra ID documentation.
-
Global Administrator privileges for your Entra ID tenant.
-
The
family_name
orgiven_name
fields populated for your users in Entra ID.
Procedures
Choose the tab for your preferred authentication protocol.
-
SAML
-
OIDC
To configure federated and SSO authentication using SAML with Entra ID as your identity provider (IdP), you must complete 3 procedures in the following order:
Start by creating a new application with Entra ID. Use the information from your enterprise application in Entra to create a realm in Capella.
-
Sign in to the Microsoft Entra admin center or the Microsoft Azure Portal.
-
Do 1 of the following to go to your Enterprise Apps page:
-
In the Entra admin center, go to
. -
In the Azure Portal, open Microsoft Entra ID, then go to
.
-
-
Click New application.
-
In the search bar, search for the Couchbase Capella - SSO application.
-
Enter a meaningful display name for the new application.
-
Click Create.
The Overview page of the app appears once it’s created.
-
Go to
. -
Choose SAML.
-
Under SAML Signing Certificates, next to the Token Signing Certificate, click Edit.
-
Click New Certificate.
-
Click Save.
-
Next to the new certificate, go to
. -
Confirm that you want to make the certificate active.
-
Next to the new certificate, go to
.Keep the certificate file open in a text editor for creating your Capella realm.
-
Keep the SAML configuration page for your Capella application in Entra ID open while creating your Capella realm.
After you have created an application with Entra ID, you need to create a realm in Capella. To create a realm, you need some information from Entra ID.
-
In Capella, click
. -
Click
. -
In the SAML Signing Certificate field, paste the contents of the downloaded PEM certificate from Entra ID, removing the first and last lines (
-----BEGIN CERTIFICATE-----
and-----END CERTIFICATE-----
)If you need to update your signing certificate later, see Change Signing Endpoint URL and Certificate. -
Copy the Login URL from Entra ID to Capella.
-
In Entra ID, under your Capella application name, copy the Login URL.
-
In Capella, paste the copied URL into the Sign-in Endpoint URL field.
-
Verify that the remaining SAML protocol settings are as follows:
Field Value Signature Algorithm
RSA-SHA256
Digest Algorithm
SHA256
SAML Protocol Binding
HTTP-POST
-
Choose a default team.
Capella automatically assigns users to the chosen default team when they do not match any team based on their SSO groups. All users assigned to the default team have its chosen permission set.
For more information, see Map User Roles.
-
Choose to turn on or off group mapping.
Group mapping allows you to assign roles to SSO users based on which teams map to their SSO group.
If you do not use group mapping, Capella uses the default team to give SSO users their roles when they first sign in. Without group mapping, you must manage your users' organization roles using the People tab and project roles using each project’s Collaborators tab.
-
-
Click Create Realm.
Capella creates the new realm with an auto-generated name.
Users need to know the realm name to sign in with SSO. You can change the a realm name after you create the realm. For more information, see Change the Realm Name.
Add the Entity ID, Callback URL, and Sign on URL from your Capella realm to your Entra ID configuration. You need to have both Capella and Entra ID open in your browser.
-
In Capella, show the Realm Summary for the realm you created for this configuration.
-
Click
. -
In the realm listing, click the arrow to show the Realm Summary.
-
-
In Entra ID, next to Basic SAML configuration, click Edit.
-
Add the Entity ID to Entra ID:
-
In Capella, copy the Entity ID field.
-
In Entra ID, in the Identifier field, paste the Entity ID.
-
-
Add the Callback URL to Entra ID:
-
In Capella, copy the Callback URL field.
-
In Entra ID, in the Reply URL field, paste the Callback URL.
-
-
Add the Sign on URL to Entra ID:
-
In Entra ID, in the Sign on URL field, paste
https://cloud.couchbase.com/enterprise-sso
.
-
-
In Entra ID, click Save.
-
Add optional claims to Entra ID:
-
In Entra ID, click Token configuration.
-
Click Add groups claim.
-
In the Edit groups claim flyout, select all the group types.
-
Click Add.
Microsoft Entra limits the total number of groups emitted in a token for SAML assertions to 150. If you have a user that’s in more than 150 groups on Entra ID, their group claims do not emit properly to Capella. To avoid group claims limits, make sure to filter your groups to only the groups you need for Capella. -
On the Optional claims page, click Add optional claim.
-
In the Add optional claim flyout, choose the SAML option.
-
Select the email claim.
-
Click Add.
-
In the dialog box, select Turn on the Microsoft Graph email permission.
-
Click Add.
-
-
Assign users to the application.
-
Add the users and groups whose members need access to Couchbase Capella.
For more information, see Quickstart: Create and assign a user account in the Azure documentation.
-
To configure federated and SSO authentication using OIDC with Entra ID as your identity provider (IdP), you must complete 3 procedures in the following order:
Start by registering an application with Entra ID. You need information from your registered application to create a realm in Capella.
-
Sign in to the Microsoft Entra admin center.
-
Click
. -
Click New registration.
-
Configure the basic settings:
-
Name: Enter a meaningful display name for this application.
-
Supported account types: Choose who can use this application. Typically, this is the default option—Accounts in this organizational directory only.
-
Redirect URI: Leave empty for now—you’ll add this later.
-
-
Click Register.
With an application registered with Entra ID, you need to create a realm in Capella. To create a realm, you need some information from Entra ID.
-
In Capella, click
. -
Click
. -
Add the OpenID Connect Discovery URL to your realm configuration.
-
In Entra ID, on your new app’s Overview page, click Endpoints
-
On the Endpoints flyout, copy the OpenID Connect metadata document field.
-
In Capella, paste the URL into the OpenID Connect Discovery URL field.
-
-
Add the Client ID to your realm configuration.
-
In Entra ID, on your new app’s Overview page, copy the Application (client) ID.
-
In Capella, paste the Client ID into the Client ID field.
-
-
Create and add the Client Secret to your realm configuration.
The secret is only shown once. You must copy it at the time of creation. If you forget to copy the secret value, you must create a new one. -
In Entra ID, on your new app’s Overview page, click Add a certificate or secret.
-
Click New client secret.
-
Enter an optional description and choose the expiration time frame.
-
Click Add.
-
Copy the secret Value.
-
In Capella, paste the Value into the Client Secret field.
-
-
Configure scopes:
Scopes determine which user information Capella requests from your identity provider. The
openid
,email
, andprofile
scopes are automatically included in the realm by default, so you do not need to add them.When adding additional scopes, separate each entry with a space.
-
Configure a default team and group mapping.
-
Choose a default team.
Capella automatically assigns users to the chosen default team when they do not match any team based on their SSO groups. All users assigned to the default team have its chosen permission set.
For more information, see Map User Roles.
-
Choose to turn on or off group mapping.
Group mapping allows you to assign roles to SSO users based on which teams map to their SSO group.
If you do not use group mapping, Capella uses the default team to give SSO users their roles when they first sign in. Without group mapping, you must manage your users' organization roles using the People tab and project roles using each project’s Collaborators tab.
-
-
Click Create Realm.
Capella creates the new realm with an auto-generated name.
Users need to know the realm name to sign in with SSO. You can change the a realm name after you create the realm. For more information, see Change the Realm Name.
Copy the Application ID, Redirect URI, and optional claim information from your Capella realm to your Entra ID configuration. You need to have both Capella and Entra ID open in your browser.
-
In Capella, show the Realm Summary for the realm you created for this configuration.
-
Click
. -
In the realm listing, click the down arrow to show the Realm Summary.
-
-
Add the Redirect URI to Entra ID:
-
In Capella, copy the Callback URL field.
-
In Entra ID, on the Overview page of the registered application, click Add a Redirect URI.
-
Click Add a platform.
-
In the Configure platforms flyout, click Web.
-
Paste the Callback URL into the Redirect URIs field.
-
Select ID tokens (used for implicit and hybrid flows).
-
Click Configure.
-
-
Add optional claims to Entra ID:
-
In Entra ID, click Token configuration.
-
Click Add groups claim.
-
In the Edit groups claim flyout, select all of the group types:
-
Security groups
-
Directory roles
-
All groups
-
Groups assigned to the application
-
-
Click Add.
-
On the Optional claims page, click Add optional claim.
-
In the Add optional claim flyout, choose the ID token type and select the following claims:
-
email
-
family_name
-
given_name
-
-
Click Add.
-
In the dialog box, select Turn on the Microsoft Graph email permission and click Add.
-
-
Assign users to the application.
-
Add the users and groups whose members need access to Couchbase Capella.
See Quickstart: Create and assign a user account in the Azure documentation for more detail.
-