How to Configure Microsoft Entra ID Single Sign-On (SSO) in CurrentWare Cloud

How to Configure Microsoft Entra ID Single Sign-On (SSO) in CurrentWare Cloud

How to Configure Microsoft Entra ID Single Sign-On (SSO) in CurrentWare

Overview

CurrentWare supports Single Sign-On (SSO) using Microsoft Entra ID through OpenID Connect (OIDC). This integration allows users to sign in to the CurrentWare Web Console using their organization's Microsoft Entra ID credentials.

This guide walks you through registering an application in Microsoft Entra ID, configuring the required authentication settings, and connecting Microsoft Entra ID to CurrentWare.

Before You Begin

You will need:

  • Microsoft Entra ID administrator access

  • Access to the CurrentWare Web Console

  • Your CurrentWare OIDC Redirect URI (provided by CurrentWare)

Step 1: Register an Application in Microsoft Entra ID

  1. Sign in to the Microsoft Entra Admin Center.

  2. Go to Microsoft Entra ID → App registrations.

  3. Click New registration.

  4. Enter a name for the application (for example, CurrentWare OIDC).

  5. Under Supported account types, select Accounts in this organizational directory only (Single tenant).

  6. Click Register.

Your application is now registered in Microsoft Entra ID.

Step 2: Configure Authentication

  1. Open your newly created application.

  2. Select Authentication.

  3. Click Add a platform.

  4. Select Web.

  5. Enter the following Redirect URI:

https://cw-saas-use2-prod-customer-portal-auth.auth.us-east-2.amazoncognito.com/oauth2/idpresponse

  1. Click Configure.

Important: The Redirect URI must match the URL provided by CurrentWare exactly, including the protocol, hostname, and path. An incorrect Redirect URI can result in an AADSTS50011 error during authentication.

Step 3: Enable ID Tokens

  1. While on the Authentication page, locate Implicit grant and hybrid flows.

  2. Enable ID tokens (used for implicit and hybrid flows).

  3. Leave Access tokens unchecked unless specifically required.

  4. Click Save.

This setting enables ID tokens for authentication flows that require them.

Step 4: Create a Client Secret

  1. In your application, select Certificates & secrets.

  2. Select Client secrets.

  3. Click New client secret.

  4. Enter a description (for example, CurrentWare OIDC).

  5. Select an expiration period (for example, 12 months, or according to your organization's security policy).

  6. Click Add.

  7. Copy the Value of the newly created client secret and store it securely.

Important: Microsoft Entra ID displays the Client Secret Value only once. If you leave or refresh the page without saving it, you must create a new secret.

Be sure to copy the Value, not the Secret ID. CurrentWare requires the Client Secret Value.

Step 5: Configure API Permissions

  1. Open your application and select API permissions.

  2. Click Add a permission.

  3. Select Microsoft Graph.

  4. Choose Delegated permissions.

  5. Add the following permissions:

    • openid

    • profile

    • email

  6. Click Add permissions.

Additional permissions, such as offline_access and User.Read, may be configured if required by your organization's authentication policies.

If required by your organization's policies, click Grant admin consent to approve the configured permissions.

Step 6: Collect Your Microsoft Entra ID Configuration Details

CurrentWare requires three values from your Microsoft Entra ID configuration:

  • Application (Client) ID

  • Client Secret Value

  • Issuer URL

Find Your Application (Client) ID

  1. In Microsoft Entra ID, go to App registrations.

  2. Open your CurrentWare OIDC application.

  3. Select Overview.

  4. Copy the Application (client) ID.

This value will be used as the Client ID in CurrentWare.

Find Your Client Secret

Use the Client Secret Value saved in Step 4.

If you did not save the value when it was created, you must generate a new client secret.

Find Your Issuer URL

The Issuer URL identifies your Microsoft Entra ID tenant and is used by CurrentWare to discover the authentication endpoints.

  1. In the Microsoft Entra Admin Center, navigate to Microsoft Entra ID → App registrations.

  2. From the App registrations page, click Endpoints without opening an individual application.

  3. Locate the OpenID Connect metadata document URL.

Example metadata URL:

https://login.microsoftonline.com/<tenant-id>/v2.0/.well-known/openid-configuration

  1. Remove /.well-known/openid-configuration from the end of the URL.

Your Issuer URL should follow this format:

https://login.microsoftonline.com/<tenant-id>/v2.0

Replace <tenant-id> with your organization's Directory (tenant) ID, which is available on your application's Overview page.

For example, if your Directory (tenant) ID is 18354e3d-8d1c-42d0-9e50-2a4780cca881, your Issuer URL would be:

https://login.microsoftonline.com/18354e3d-8d1c-42d0-9e50-2a4780cca881/v2.0

Important: Use your organization's actual Directory (tenant) ID. Do not use the example value shown above.

Step 7: Configure SSO in CurrentWare

  1. Sign in to the CurrentWare Web Console.

  2. Navigate to Administration → Single Sign-On (SSO).

  3. Configure the following settings:

SettingValue
ProviderOIDC
Enable SSOEnabled
Client IDApplication (client) ID from Microsoft Entra ID
Client SecretClient Secret Value from Microsoft Entra ID
Authorized Scopesopenid email profile
Endpoint DiscoveryAutomatic (Issuer URL)
Issuer URLYour Microsoft Entra ID Issuer URL
  1. Click Save to apply the configuration.

Step 8: Verify the SSO Configuration

After saving the configuration, test the integration to confirm that users can authenticate successfully.

  1. Open a new Incognito or InPrivate browser window.

  2. Navigate to your CurrentWare login page.

  3. Click Sign in with SSO.

  4. Sign in using your Microsoft Entra ID credentials.

  5. Confirm that you are redirected back to the CurrentWare Web Console and successfully signed in.

If authentication completes successfully, your Microsoft Entra ID SSO integration is configured.

Troubleshooting

  • AADSTS50011 – Redirect URI mismatch: Verify that the Redirect URI configured in Microsoft Entra ID matches the URL provided by CurrentWare exactly.

  • Invalid Client Secret: Confirm that you entered the Client Secret Value, not the Secret ID. Check whether the secret has expired.

  • Authentication fails or the identity provider cannot be reached: Verify that the Issuer URL contains the correct Directory (tenant) ID and ends with /v2.0.

  • User cannot sign in: Confirm that the user has access to the application in Microsoft Entra ID and that any required administrator consent has been granted.

  • SSO option does not appear in CurrentWare: Verify that SSO is enabled and the OIDC configuration has been saved.

Tags: Cloud, SSO, Microsoft Entra ID, OIDC, Authentication, Integrations