Applications federated through Microsoft Entra ID (formerly Azure AD) may not pass users' identities to Entra ID after the initial login. When this occurs, the application redirects users to Entra ID, which prompts them to re-authenticate. To avoid a second login prompt, you can add parameters that contain the user's identity information to the application URL in RapidIdentity.
- Log in to your RapidIdentity Administrator portal.
- In the Dashboard pop-up menu, click Applications.
- Click Catalog.
- Locate the application tile in the catalog and click the ellipsis in the upper-right corner.
- Click Details.
- In the Details tab, click Edit.
- In the Application URL field, add the following parameters to the URL:
- Object ID
- The ID from the application registration in Microsoft Entra ID
- Tenant ID
- Your Microsoft Entra ID tenant ID
- login_hint
- Uses the RapidIdentity attribute
%idautoPersonSAMAccountName% and your organization's domain to pre-populate the username in Microsoft Entra IDNote:The attribute used may vary depending on your organization's username format and domain configuration.
- domain_hint
- Identifies the user's domain to Microsoft Entra ID
- Domain
- Your organization's domain
The following is an example application URL:
https://launcher.myapps.microsoft.com/api/signin/<Object ID>?tenantId=<Tenant ID>&login_hint=%idautoPersonSAMAccountName%@<Domain>&domain_hint=<Domain> - Click Save.
The application passes the users' identity to Microsoft Entra ID, and the user does not need to re-authenticate.