Access Manager 6.1sp4 and 6.2 Broke I18N internationalization support in AdminGUI
Originally Published: 2015-10-06
Article Number
Applies To
6.1 SP4
6.2
Issue
# Specifies list of characters that are allowed to key in # in the Admin GUI console. # # # Default Value: # ,.:@;#$\\-!_ *'\"\\\\\\/?=~ # # #cleartrust.admingui.allowed.characters=,.:@;#$\\-!_ *'\"\\\\\\/?=~
This Broke I18n support
The following error would display trying to use 8 bit characters with the above default setting and the I18n filter configured:
"This string has characters that are not allowed in this field"
Even using the above parameter with no value produced the same error
example:
cleartrust.admingui.allowed.characters=
Cause
Java regular expression words are only in us-ascii so any non-us-ascii charcaters would get rejected, thus breaking I18n support
Resolution
To use international charcters, such as French, Contact customer Support to request the latest hotfix containing the latest version of admingui.
Modify the admnigui.cgf file to comment out the allowed characters parameter
#cleartrust.admingui.allowed.characters=
Refer to the Installation And Configuration guide on configuring the i18n filter for 8-bit character support only.
Related Articles
How to create FASC-N value in subjectAltName using RSA Certificate Manager API 7Number of Views Why are there N/A's seen in BackOffice Cases Transactions and Reports? 9Number of Views Oracle Collector Error "Non supported character set (add orai18n.jar)" in SecurID Governance & Lifecycle 84Number of Views AIX - Syslogd flag -n should not be used (AIX event source not discovered) 14Number of Views 'com.aveksa.server.db.PersistenceException:n/a' errors when importing business source metadata into RSA Identity Governanc… 241Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?