Microsoft Entra ID Custom Controls - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide
Before You Begin
- Install Microsoft Entra Connect and synchronize your on-premise AD. This is the same on-premise AD configured in RSA as an Identity source.
- Configure at least one Entra cloud application.
Important Note
This configuration is not supported for customers in the GCC High Environment.For more details, refer to: https://community.rsa.com/s/article/Microsoft-365-Government-Community-Cloud-Conditional-Access
Configure RSA Access Policies
Procedure- Sign in to RSA Cloud Administration Console.
- Navigate to Access >Policies.
- Click Add a policy.
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as Relying Party to Microsoft Entra ID Custom Controls.Procedure
- Sign in to RSA Cloud Administration Console.
- Click Authentication Clients > Relying Parties.
- On the My Relying Parties page, click Add a Relying Party.
- On the Relying Party Catalog page, click Add for Microsoft Entra ID.
- On the Basic Information page, enter a name for the Microsoft Entra ID Relying Party instance in the Name field.
- Click Next Step.
- On the Authentication page, select the policy that you have configured, and click Next Step.
- On the Connection Profile page:
- The Authorization Server Issuer URL is a generated value that will be needed later to configure Entra ID.
- In the Relying Party Issuer URL, enter the value: https://sts.windows.net/<AZURE-TENANT-ID> replace the AZURE-TENANT-ID with the Entra Tenant ID. To locate your Tenant ID, log on to the Entra admin portal and navigate to Identity > Overview, and copy the Tenant ID.
- Enter the Client ID. This can be any value but it must match the ClientID configured in Entra.
- Azure Active Directory Application ID: bfda057e-d676-4c42-9742-6eea99bbedc1
- Click Save and Finish.
- Click Publish Changes.
Configure Microsoft Entra ID
- Log on to Entra Portal - entra.microsoft.com using your administrator credentials.
- In the left pane, scroll down to Protection > Conditional access.
- On the Conditional access page, click Custom controls.
- Click + New custom control. A window with a JSON script opens.
- Replace the default script with the metadata file copied from the RSA Console. Navigate to Authentication Clients > Relying Parties. Click the Edit drop-down icon and click Metadata against the application created. Copy and paste the script into the JSON window.
- Name: Must be unique between all Custom controls.
- AppID: Enter bfda057e-d676-4c42-9742-6eea99bbedc1.
- ClientID: Enter the Client ID value from step 8c in the Configure RSA Cloud Authentication Service section.
- DiscoveryUrl: Enter the Authorization Server Issuer URL appended by /.well-known/openid-configuration.
- Id: Must be unique between all Custom controls.
- Name: Same as Id.
- Type: Enter mfa-policy.
- Value: A single space between quotes. Enter the JSON for customized controls given by your claim providers. See the following example.
- Click Create.
- On the Conditional access menu, click Policies > + New policy.
- Enter a name for the new policy; for example, Protect Sales Applications.
- Under Assignments, select Users and groups.
- Select the users who require additional authentication.
- On the Users and groups window, click Done.
Note: To avoid the administrator account locking out, click the Exclude tab and exclude the administrator from this policy. - Under Assignments, select Target resources.
- On the Cloud apps > Include window, select the apps this policy will apply to.
- On the Cloud apps window, click Select.
- Select Access controls.
- Click Grant.
- On the Grant window, select Grant access and select the Custom control that you created.
- Click Select.
- Select On to enable the policy.
- Click Create.
User Experience
- Log on to the Microsoft Entra application portal.
- Select a protected application. This will redirect you to RSA for additional authentication.
- Authenticate based on your method of authentication set in RSA.
Return to Microsoft Entra ID Custom Controls - RSA Ready Implementation Guide .
Related Articles
Microsoft Entra ID Custom Controls - RSA Ready Implementation Guide 53Number of Views Microsoft Entra ID - RSA Ready Implementation Guide 245Number of Views Microsoft Entra ID External Authentication Methods (EAM) - RSA Ready Implementation Guide 540Number of Views Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 502Number of Views Microsoft Entra ID - SCIM Client for Cloud Authentication Service - RSA Ready Implementation Guide 523Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process How to factory reset an RSA Authentication Manager 8.x hardware appliance without a factory reset button from the Operatio… Deploying RSA Authenticator 6.2.2 for Windows Using DISM
Don't see what you're looking for?