Azure AD / Entra ID

Setting up SAML2.0 SSO with Azure AD / Microsoft Entra ID as an IdP for Currents

circle-info

Enabling SSO will affect all users of your organization, users would not be able to sign in to Currents using a different authorization method when SSO is enabled.

Supported Features

  • SP-initiated SSO (Single Sign-On)

  • Just-In-Time provisioning

Setup Steps

1

Create Enterprise Application

  1. Navigate to Microsoft Entra ID (formerly Azure Active Directory)

  2. Go to Enterprise applications > New application

  3. Click Create your own application

  4. Enter a name (e.g., "Currents") and select Integrate any other application you don't find in the gallery (Non-gallery)

  5. Click Create

2

Configure SAML Single Sign-On

  1. In your new application, go to Single sign-on in the left menu

  2. Select SAML as the single sign-on method

  3. In the Basic SAML Configuration section, click Edit and set:

Setting
Value

Identifier (Entity ID)

urn:amazon:cognito:sp:us-east-1_Z9TVEnj0k

Reply URL (ACS URL)

https://auth.currents.dev/saml2/idpresponse

  1. Click Save

3

Configure User Attributes and Claims

circle-exclamation

Unique User Identifier (Name ID)

Configure Entra to send the user's lowercase email as NameID attribute.

  1. In the Attributes & Claims section, click Edit

  2. Open the Unique User Identifier (Name ID) claim

    1. claim name nameidentifier;

    2. namespace http://schemas.xmlsoap.org/ws/2005/05/identity/claims

  3. Under Choose name identifier format, set Name identifier format to Persistent.

  4. Under Source, select Transformation (not Attribute).

  5. Set Transformation to ToLowercase with input user.mail — the portal displays this as ToLowercase (user.mail).

  6. Click Save

Additional claims

Under Attributes & Claims, in Additional claims, click Add new claim for each row below. Use SAML as the claim type where the portal asks for it.

Claim Name
Value

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

Transformation ToLowercase with source user.mail (shown as ToLowercase (user.mail)).

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

user.displayname

circle-info

Use the ToLowercase transformation for email values so mixed-case addresses from Azure AD match Currents accounts.

Microsoft Entra Attributes Mapping Example
4

Download Federation Metadata

  1. In the SAML Certificates section, locate Federation Metadata XML

  2. Click Download to save the metadata file

  3. Open the downloaded XML file and verify it contains both HTTP-POST and HTTP-Redirect bindings:

<SingleSignOnService 
    Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" 
    Location="https://login.microsoftonline.com/..." />
<SingleSignOnService 
    Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" 
    Location="https://login.microsoftonline.com/..." />
5

Share Configuration with Currents

Contact Currents support ([email protected] or via in-app chat) and provide:

  • The downloaded Federation Metadata XML file

  • List of email domains your organization uses (e.g., @example.com, @example.org)

Currents support will configure your SSO integration and notify you when it's ready.

6

Assign Users

  1. In your Enterprise application, go to Users and groups

  2. Click Add user/group

  3. Select the users or groups who should have access to Currents

  4. Click Assign

7

Test the Integration

Once Currents support confirms the integration is active:

  1. Enter your email address and click Continue

  2. You will be redirected to Microsoft's login page

  3. After authenticating, you should be redirected back to the Currents dashboard

If you encounter errors, see Troubleshooting SSO.

Reference

For more details on SAML attribute configuration, see:

Last updated

Was this helpful?