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 After changes in certificate keystore, Help Desk Admin Portal (HDAP) and Self-Service Portal (SSP) consoles not accessible… Number of Views Generic REST Collector problems with Authentication (OAuth2, Bearer Token or Basic Authentication) in RSA Governance & Lif… Number of Views Generic REST Collector Test Authentication Token fails with 'Error encountered while fetching token, Status Code: 4… Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
