RCM: CN encoding Issues with apostrophe character
Originally Published: 2009-11-18
Article Number
Applies To
Using the apostrophe character in the CN was was not an issue when using RCM 6.7 [411]
All supported platforms
Issue
The following workaround, which was working with build 411 does not work
build 411, we needed to modify the variable "regExp" in the file "x-templates\x-enroll-msie-dn-script.xuda" to be able to submit a certificate request with the apostrophe character, as bellow:
//var regExp = new RegExp( "\[<>\047\042~!@#$^&*|\134;+_\]" );
var regExp = new RegExp( "\[<>\042~!@#$^&*|\134;+_\]" );
Cause
We assume that the above changes are the custom changes and it bypasses the validation for apostrophe.
The above regex modification is working on build 411 but not working on build 423 because we have fixed vulnerability issue in RCM 6.7 build 420.
Notes
Related Articles
Generic REST Collector does not URL-encode Query Parameters in RSA Identity Governance & Lifecycle Number of Views Tokenization: Client returns error 78043 (SOM_RES_INVALID) server log shows 'PLS-00201: identifier 'RSAPSORTS' must be de… Number of Views Generic REST Collector Test Authentication Token fails with 'Error encountered while fetching token, Status Code: 4… Number of Views RSA Identity Governance and Lifecycle 7.0.x upgrade or installation fails with [FATAL] [INS-13013] and Oracle Installer Ex… Number of Views Running AFX Connectors start to fail, edited connectors remain in a Not Deployed state and 'Could not connect to broker UR… Number of Views
Trending Articles
How to download and install the AFX Server Archive in RSA Identity Governance & Lifecycle RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide The Template ({Connector Template Name}) has missing file content error when creating AFX Connectors in RSA Identity Gover… Downloading RSA Authentication Manager license files or RSA Software token seed records Troubleshooting RSA MFA Agent for Microsoft Windows
Don't see what you're looking for?
