Okta - IdP for My Page - RSA Ready Implementation Guide
This article describes how to configure Okta as an IdP for My Page.
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA My Page as a service provider for Okta.
Procedure
- Sign in to the RSA Cloud Administration console.
- Navigate to Access > My Page and ensure that the My Applications option is enabled. Users can use the displayed URL to access the self-service My Page portal.
- Create a 2.0 policy for authentication:
- Navigate to Access > Policies and click Add a Policy.
- On the Basic Information page, provide a policy name and click Next Step.
- Select the identity source that should be available for this policy and click Next Step.
- On the Primary Authentication page, enable the Primary Authentication option and select the Okta Identity Provider that is created.
- Click Next Step and make the desired changes on the Rule Sets tab.
- Click Save and Finish and click Publish Changes.
Note: Use a placeholder method until Okta Identity Provider is configured by following the steps in the Adding Identity Provider subsection and then revisit to update the Default Method.
Assigning Policy for My Page
- Go to Access > My Page > My Applications.
- Under the Authentication section, select the 2.0 access policy created before.
- Click Save and click Publish Changes.
Adding Identity Provider
- Go to Users > Identity Providers and click Add for Cloud Identity Providers.
- Enter a name for the Okta provider and provide the following details:
- In the Issuer ID field, enter the value of the Issuer ID provided by Okta: http://www.okta.com/AccountID. This is the value of Issuer copied from Okta.
- In the Issuer URL field, enter the value of the Sign-on URL copied from Okta
- In the Audience ID field, provide any value. This value is included by the identity provider in SAML assertions to indicate the intended recipient. The value is set as the Entity ID in SAML requests sent to the identity provider. We have given the hostname of the Cloud authentication service tenant along with “.com”.
- Copy the Assertion Consumer Service (ACS) URL and Audience ID to be used in the Okta configuration.
- In the Certificate section, click Choose File to upload a certificate that the Cloud Authentication Service uses to validate the assertion signature provided by Okta. This is the certificate downloaded from the Okta side. Refer to the Configure Okta section to obtain the certificate to validate the assertion signature.
- Ensure that an Identity source is created in RSA Cloud Authentication Service under Users > Identity Sources or create a local one for testing purposes. Create a new user in the local identity source. This user will be able to access the My Page portal.
- Click on Save and Finish and click Publish Changes.
Configure Okta
Perform these steps to configure Okta as the third-party IdP for My Page.
- Sign in to Okta Admin Console.
- In the left side panel, click Applications > Applications.
- Click Create App Integration.
- Select SAML 2.0.
- In the General Settings section, enter a name for the application (My Page portal) and then click Next.
- Perform the following steps to create a new application in Okta.
- Provide the App name in the General Settings section and click Next.
- Provide random acceptable values for Single sign-on URL, Audience URI, and click Next.
- Select the This is an internal app that we have created checkbox and click Finish.
Note: The values given in the preceding step are placeholder values in order to create the application in Okta and generate the values required for the configuration on RSA.
- Go to the Sign On tab of the created application and copy the values of Issuer and Sign on URL to be used in RSA configuration.
- Download the Signing Certificate. This will be used on the RSA side of the configuration.
- Go to the General tab of the created application and click edit on the SAML Settings.
- On the Configure SAML tab, provide the following details:
- Single sign-on URL: Enter the value of ACS URL that was copied from RSA.
- Audience URI (SP Entity ID): Enter the value of the Audience ID that was copied from RSA.
- Name ID format: Set this to EmailAddress.
- Set the rest of the values to default values .
- Click Next.
- Select the This is an internal app that we have created checkbox.
- Click Finish.
- Assign the users who will be able to access the created application by performing the following steps. These are the users who will be able to log in to My Page after being authenticated by Okta.
- Click the Assignments tab on the newly created application.
- Click Assign > Assign to People.
- Search for the user and click Assign against the user.
The configuration is complete. The users can sign in to My Page and be authenticated by Okta.
Return to Okta - Third-Party IdP Integration - RSA Ready Implementation Guide.
Related Articles
Okta Agent - RSA Ready Implementation Guide 6Number of Views Okta - IdP for Cloud Authentication Service - RSA Ready Implementation Guide 57Number of Views Okta - RSA Ready Implementation Guide 110Number of Views ManageEngine ADSelfService Plus - RADIUS Configuration - RSA Ready Implementation Guide 1Number of Views RSA October 2023 Release Announcements 37Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Supported On-Demand Authentication (ODA) SMS providers for use with RSA Authentication Manager 8.x
Don't see what you're looking for?