Certified: April 01, 2025
Solution Summary
This article describes the configuration steps in adding ID Dataweb as a user Identity Verification Provider for RSA Cloud Authentication service using OIDC.
After ID Dataweb is added as a user Identity Verification Provider, it can be used in the My Page enrollment and recovery policies.
Use Case
ID Dataweb can be integrated with RSA as an Identity Verification Provider for Cloud Authentication Service using OIDC. For details on overview and solution summary, see RSA & ID Dataweb - Identity Verification.
Configuration Summary
This section contains instruction steps that show how to configure ID Dataweb with RSA Cloud Authentication Service as a user Identity Verification Provider.
This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products to install the required components.
All RSA and ID Dataweb components must be installed and working prior to the integration.
Configure RSA Cloud Authentication Service
Perform the steps in this section to configure ID Dataweb as a User Identity Verification Provider.
Prerequisites
- Identity sources with valid users must be configured, or a local user must be created.
- The required attributes, as mentioned in the ID Dataweb documentation for the respective workflow, must be synchronized with the RSA Cloud Authentication Service after the identity source is added.
- My Page enrollment policy or My Page recovery policy under Access > My Page > Enrollment and Recovery tab must be enabled and configured.
- An active ID Dataweb and RSA account (with Super Administrator privileges).
- Follow the instructions in ID Dataweb documentation to set up your ID Dataweb tenant.
Configure Attributes in RSA for ID Dataweb Workflow
Procedure
- Sign in to Cloud Administration Console as Customer Super Admin.
- Create and synchronize Identity Source.
- Navigate to Access > OIDC Settings > Scopes and define a new scope called 'openid'.
- Make a note of the attributes required by ID Dataweb workflow and identify the equivalent attributes in Identity Source in Cloud Authentication Service. For this use case, first name and last name attributes are sent.
For the latest list of allowable attributes, refer to the ID Dataweb documentation.ID Dataweb Attribute Description Identity Source Attribute in Cloud Authentication Service fname First Name givenname lname Last Name sn - Navigate to Users > Identity Sources and select the identity source added.
- Click the User Attributes tab and make sure that the preceding Identity Source Attributes are available to access the policy configuration.
- Click Next Step and make sure that mappings for First Name and Last Name attributes are correct.
- Ensure that the Synchronize user attributes checkbox is selected.
- Click Next Step > Save and Finish.
- Click Publish Changes.
Configure Identity Verification Provider Connector
Procedure
- Navigate to Users > Identity Verification Providers.
- Click the Attribute Mapping tab.
- (Optional) Provide the Attribute Names you wish to pre-send. We send first name and last name for our use case. Select the identity source and the value. Make sure that the values are stored as expected by ID Dataweb. For example, make sure givenName (as shown in the screenshot) has the first name of the user stored.
- Browse to the well-known URL for production and copy the data that will be used in the next steps.
- Click the Identity Verification Providers tab and click Add against ID Dataweb.
- Perform the following steps:
- In the Name field, enter a name.
- (Optional) In the Description field, enter a description.
- Set Issuer ID as the value of issuer from the well-known URL.
- Set Authorization Endpoint as the value of authorization_endpoint from the well-known URL.
- Set Token Endpoint as the value of token_endpoint from the well-known URL.
- Set Client ID as the Primary Service API Key value copied from ID Dataweb. (Refer to the Configure ID Dataweb section.)
- Set Client Secret as the Shared Secret value copied from ID Dataweb. (Refer to the Configure ID Dataweb section.)
- (Optional) Select any Attribute Mappings added in the Attribute Mapping tab earlier.
- Set Scope as openid.
- Make a note of the Redirect URI generated. This will be used when configuring ID Dataweb.
- Set Provider Public Key.
- To get the value of ID Dataweb's public key, open the jwks_uri in a browser from the well-known URL. Copy the public key starting with
"-----BEGIN PUBLIC KEY-----" and ending with "-----END PUBLIC KEY-----".”\n” in the beginning and end of the key signifies new line and should not be included (Refer to the preceding screenshot).
- To get the value of ID Dataweb's public key, open the jwks_uri in a browser from the well-known URL. Copy the public key starting with
- Click Save and Finish.
- Click Publish Changes.
Configure My Page Enrollment and My Page Recovery Policies
Procedure
- Navigate to Access > My Page and perform the following steps:
- To use identity verification for the self-enrollment of users on My Page, on the Enrollment and Recovery tab, enable the allow users self-enrollment option.
- Click Save and click Publish Changes.
- To use identity verification for the self-enrollment of users on My Page, on the Enrollment and Recovery tab, enable the allow users self-enrollment option.
- Navigate to Access > Policies and perform the following steps:
- Click Enable corresponding to My Page Enrollment Policy.
- Select the applicable identity sources and click Next Step.
- Make applicable changes on the Rule Sets tab and select Password + Identity Verification Providers as the Method for Identity Verification.
- In the Identity Verification Provider list, select the Identity Verification Provider created.
- Click Save and Finish.
- Click Publish Changes.
- Click Enable corresponding to My Page Recovery Policy.
- Select the applicable identity sources and click Next Step.
- Make applicable changes on the Rule Sets tab and select Password + Identity Verification Providers as the Method for Identity Verification.
- In the Identity Verification Provider list, select the Identity Verification Provider created.
- Click Save and Finish.
- Click Publish Changes.
- Click Enable corresponding to My Page Enrollment Policy.
Notes
- My Page enrollment policy can only be used for users who do not have a registered authenticator. My Page recovery policy can only be used for users who have at least one authenticator registered. For more details, refer to the Set Up Enrollment and Recovery Settings section in the Manage My Page article.
- Adding attributes in the Attribute Mapping tab of the connector is an optional step. Refer to ID Dataweb documentation for further details on the supported attributes and format for prefilled information.
- At the time of testing this document, the well-known URL used for the production is https://prod2.iddataweb.com/axn/oauth2/.well-known/openid-configuration. Refer to the ID Dataweb documentation for the latest well-known URLs.
Configure ID Dataweb
Perform these steps to configure ID Dataweb.
Procedure
- Log in to ID Dataweb admin console.
- In the left pane, click Workflows.
The available templates are displayed. - Select a template based on your business requirements.
- Click the drop-down arrow against the template for the desired workflow (in this instance, the workflow template of BioGovID is used) and select Open Workflow Details.
- Click the eye icon against Primary Service API Key and Shared Secret and copy the values. Use these values in the Client ID and Client Secret fields respectively in RSA configuration.
- Click Actions in the upper-right corner and select Start Change request.
- Click Start Change Request.
- Scroll down to the Customer Redirect URLs section and click Add Customer Redirect URL.
- Paste the Redirect URI value copied from the RSA configuration into the Redirect URL field and click Save.
- In the upper-right corner, click Save.
- Click on Actions > Deploy Changes Now to deploy the changes made.
The configuration is complete.
User Experience
The configured Identity Verification Provider can be used:
- For the self-enrollment of users on My Page.
- For the recovery of access to the user accounts in case of lost/damaged/stolen authenticator.
You can test the integration by configuring either of these or both. The following section shows the BIOGovID workflow behavior for self-enrollment.
Self-Enrollment
- Navigate to Access > My Page > Enrollment and Recovery.
- Copy the Enrollment URL and browse to this URL in a browser.
- Enter the e-mail address of the user and click Submit.
- On the next screen, enter the user's password and click Submit.
- Select the Country and click Continue.
- Provide the phone number of the user and click Confirm Information.
The user is shown the following message while the given phone number receives a verification link.
Once all the necessary documents are uploaded and the process is completed, ID Dataweb shows a success message (if the provided information is valid), and the user is allowed into My Page.
RSA Terminology Changes
The following table describes the differences in the terminologies used in the different versions of RSA products and components.
| Previous Version | New Version | Examples/Comments |
| Company ID | Organization ID | |
| Account | Credential | |
| Token | OTP Credential | SecurID OTP Credential |
| Tokencode | OTP/Access Code | SecurID OTP, SMS OTP, Voice OTP Emergency Access Code, Disable Access Code |
| Hardware Token | Hardware Authenticator | |
| Device Serial Number | Binding ID | |
| Device | Credential/Authenticator | |
| Device Registration Code | Registration Code | |
| Authenticate App | Authenticator App |
Certification Details
RSA Cloud Authentication Service
ID Dataweb
Known Issues
No known issues.
Related Articles
GoToMeeting - RSA Ready Implementation Guide 42Number of Views RSA SecurID Authentication Engine 2.8.2 for Java Release Notes 3Number of Views Okta - Third-Party IdP Integration - RSA Ready Implementation Guide 54Number of Views Specops Software uReset - SecurID Authentication API with CAS Configuration - RSA Ready SecurID Access Implementation Guide 21Number of Views Ping Directory- Identity Source Integration - RSA Ready Implementation Guide 16Number 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