Skip to main content
All CollectionsTroubleshooting & Support
Managing your Azure AD/Entra ID Secret with Coram
Managing your Azure AD/Entra ID Secret with Coram

Learn how to create, manage, and renew your Azure AD/Entra ID application client secret with Coram to avoid or fix authentication issues.

Updated over a month ago

💡 At a Glance

A vital part of Integrating Coram with Azure AD/Entra ID single sign-on (SSO) is managing your application client secret, which authenticates Coram’s connection to your Azure AD/Entra ID tenant. Proper management and timely renewal are essential to maintain SSO functionality and avoid authentication issues.

Key Tasks

  • Set Up Your Secret with Coram
    Register a new application in your Azure AD/Entra ID portal, create a client secret with an appropriate expiry duration, and provide the secret to Coram support to establish the SSO connection.

  • Monitor Secret Expiration and Ensure Timely Renewal

    Keep track of your secret’s expiration date by setting up renewal reminders, and generate a new client secret before the current one expires. Then contact Coram support and provide them with your new secret.

  • Troubleshoot SSO Issues

    If SSO stops working, check whether the client secret has expired. Renew the secret if necessary and confirm the update with Coram support to restore access.

For detailed information, keep reading below.

Overview

Integrating Coram with Azure AD/Entra ID provides a seamless login experience for your organization’s users. When you enable SSO, users can access Coram using their existing Azure AD/Entra ID credentials. A critical component of this setup is an application client secret, sometimes referred to as the secret. Your secret authenticates Coram’s connection to your Azure AD/Entra ID tenant and enables SSO functionality.

Important:

  • Your organization may have a security policy that mandates an expiration period for your secret, which requires monitoring and renewal.

  • If your secret expires without renewal, SSO stops working, and you will not be able to access your Coram account until you generate a new secret and contact Coram support to update it.

Setting Up your Secret during SSO Integration

When you first integrate Azure AD/Entra ID SSO with Coram, part of the process involves the creation of an application client secret in your Azure AD/Entra ID portal. You must then share this secret with the Coram support team to allow them to complete the setup process.

Note: The following section provides general information about setting up your application client secret during SSO integration. For detailed instructions, read the official Azure AD/Entra ID documentation.

Before you begin, ensure the following:

  • You know your company’s security policy regarding the expiration period for your secret.

  • You have permission to create and modify apps in your Azure AD/Entra ID portal.

  • You can coordinate directly with Coram support to finalize the integration.

To set up your secret with Coram:

  1. In your portal, go to App Registrations, and register a new application that represents Coram in your directory.

  2. Under Certificates & secrets, create a new client secret, and choose an expiry duration that matches your company’s policy.

  3. Copy the secret value immediately, as the system conceals it after you leave the page.

  4. Contact Coram support, provide them with the secret value, and request that they add it to your organization in Coram.

  5. After the secret is set, test access to your Coram account using SSO on the Coram login page.

Tip: For help with configuring and integrating your SSO with Coram, contact Coram support.

Managing and Renewing your Secret

Based on your organization's policy, your secret may expire periodically, so use your Azure AD/Entra ID portal to set up renewal reminders, or schedule manual checks.

If your secret is close to expiry, generate a new one and provide it to Coram support well before the old one expires. Coram must then update the secret in their system.

Note: You cannot update your secret independently in the Coram web app.

Once your secret is updated, confirm that it works by testing your SSO login again.

Did this answer your question?