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
RSA Governance & Lifecycle Recipes: WF Node Metrics Number of Views Generic REST Collector does not URL-encode Query Parameters in RSA Identity Governance & Lifecycle Number of Views Generic REST Collector ignores Proxy setting in RSA Identity Governance & Lifecycle Number of Views RSA Governance & Lifecycle Integration: Generic SSH and SSH-Keypair Summary Number of Views RSA Governance & Lifecycle Generic SSH and SSH-Keypair Connector Datasheet Guide Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA
Don't see what you're looking for?
