Prerequisites
Before starting, ensure you have:- Access to the Microsoft Entra Admin Center with permissions to create enterprise applications.
- A valid Microsoft Entra ID tenant.
- Admin credentials for your organization’s Microsoft Entra ID tenant.
Steps to Configure Microsoft Entra ID SAML
Follow these steps to set up SAML SSO with Microsoft Entra ID.Step 1: Create an Enterprise Application
- Log in to the Microsoft Entra Admin Center.
- Navigate to Enterprise applications in the left-hand menu.
- Click New application.
- Click Create your own application.
- Enter a name for your application (e.g.,
Roe-AI SSO Integration). - Select Integrate any other application you don’t find in the gallery (Non-gallery).
- Click Create.
Step 2: Configure SAML Single Sign-On
- In your new application, navigate to Single sign-on in the left-hand menu.
- Select SAML as the single sign-on method.
- In the Basic SAML Configuration section, click Edit and fill in:
- Identifier (Entity ID):
https://api.roe-ai.com/sso/saml/metadata/<your-organization-id>/ - Reply URL (Assertion Consumer Service URL):
https://api.roe-ai.com/sso/saml/acs/
- Identifier (Entity ID):
- Click Save.
Note: Replace <your-organization-id> with your actual organization ID from the Roe AI platform.
Step 3: Configure Attributes & Claims
- In the Attributes & Claims section, click Edit.
- Ensure the following claims are configured:
| Claim name | Value |
|---|---|
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress | user.mail or user.userprincipalname |
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname | user.givenname |
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname | user.surname |
- Click Save to apply changes.
Tip: If your users’ email addresses are stored inuserPrincipalNamerather thanuser.userprincipalnamefor the email claim.
Step 4: Download the Certificate
- In the SAML Certificates section, find Certificate (Base64).
- Click Download to download the certificate file.
- Open the downloaded file in a text editor to get the PEM-formatted certificate.
Step 5: Retrieve IdP Configuration
- In the Set up [Your App Name] section, note the following:
- Login URL: This will be used as the SAML IdP SSO URL.
- Microsoft Entra Identifier: This will be used as the SAML IdP Entity ID.
Step 6: Assign Users and Groups
- Navigate to Users and groups in the left-hand menu.
- Click Add user/group.
- Select the users or groups who should have access to the application.
- Click Assign.
Configuration on Your Platform
Once you’ve collected the necessary information from Microsoft Entra ID, configure your platform as follows:| Field | Value |
|---|---|
| SAML IdP Entity ID | The Microsoft Entra Identifier from Azure. |
| SAML IdP SSO URL | The Login URL from Azure. |
| SAML IdP X.509 Certificate | The certificate downloaded in Step 4 (PEM format). |
| SAML User Identifier Key | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress |
| SAML User First Name Key | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname |
| SAML User Last Name Key | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname |
Testing the Integration
- Log out of your account on the platform.
- Go to the login page and select Sign in with SSO.
- Authenticate through Microsoft Entra ID.
- Verify that:
- You are redirected back to the platform.
- Your user details (e.g., name, email) are displayed correctly.
Troubleshooting
- Invalid Reply URL Error:
- Ensure the Reply URL matches exactly:
https://api.roe-ai.com/sso/saml/acs/
- Ensure the Reply URL matches exactly:
- Certificate Errors:
- Verify the certificate is in PEM format (starts with
-----BEGIN CERTIFICATE-----). - Ensure you downloaded the correct certificate (Base64 format).
- Verify the certificate is in PEM format (starts with
- User Not Found:
- Verify the user has been assigned to the enterprise application.
- Check that the email claim is configured correctly.
- Attribute Mapping Issues:
- Use a SAML debugging tool to inspect the claims being sent.
- Ensure the claim names match the expected values.
- AADSTS Errors:
AADSTS700016: Application not found. Verify the Entity ID is correct.AADSTS50011: Reply URL mismatch. Check the ACS URL configuration.
For further assistance, contact our support team.