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 Generic REST Collector Test Authentication Token fails with 'Error encountered while fetching token, Status Code: 4… Number of Views Integration of Dell EMC Data Domain with RSA Authentication Manager REST API Number of Views Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Number of Views Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
