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 In RSA Via Lifecycle and Governance the Allow Multiple Selections checkbox is disabled for the User Accounts Table in the … Number of Views AFX Server fails to start and unable to create a new AFX Server on WebSphere in RSA Identity Governance & Lifecycle Number of Views Generating a Report on a Windows platform hosting Web Tier software Number of Views Generic REST Collector problems with Authentication (OAuth2, Bearer Token or Basic Authentication) in RSA Governance & Lif… Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
