Special characters in email subject lines do not display as expected in RSA Identity Governance & Lifecycle
Originally Published: 2019-04-09
Article Number
Applies To
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1
Platform: WildFly
Issue
Cause
In the case of RSA Identity Governance & Lifecycle on WildFly, the operating system environment has a default character set of ANSI_X3.4-1968, rather than UTF-8. Since the application server does not specifically override the setting, the environment default is used. This is caused by a missing JVM startup parameter in the WildFly application server startup script.
This is a known issue reported in engineering ticket ACM-95236.
Resolution
- RSA Identity Governance & Lifecycle 7.0.2 P14
- RSA Identity Governance & Lifecycle 7.1.0 P07
- RSA Identity Governance & Lifecycle 7.1.1 P02
- RSA Identity Governance & Lifecycle 7.2
Workaround
A manual edit to the startup file may be done as a workaround to this issue. Please note that this manual edit will not persist if the system is patched, and the new patch version is below the versions listed in the Resolution section. The manual edit will need to be reapplied after patches, upgrades, and hotfixes that are below the resolution versions.
The steps below provide instructions on making the manual edit to the startup file. These instructions are the same for the aveksa_server and aveksa_cluster startup scripts. The example below uses the aveksa_server startup script.
- Login to the WildFly application server as the root user.
- Backup the existing startup file:
cp /etc/init.d/aveksa_server /etc/init.d/aveksa_server_backup
- Edit the startup file:
vi /etc/init.d/aveksa_server
- Locate the JAVA_OPTS line that looks similar to the line shown below:
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.net.ssl.enableECC=false -Djava.awt.headless=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$AVEKSA_HOME $EXTRA_OPTS"
- Add the text below to the beginning of the line of JAVA_OPTS:
-Dclient.encoding.override=UTF-8 -Dfile.encoding=UTF-8
It should be something similar to:
JAVA_OPTS="$JAVA_OPTS -Dclient.encoding.override=UTF-8 -Dfile.encoding=UTF-8 -Dcom.sun.net.ssl.enableECC=false -Djava.awt.headless=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$AVEKSA_HOME $EXTRA_OPTS"
- Save the edits.
:wq!
- The change to the configuration will take effect upon the next start/restart of WildFly: Perform a restart with the command below:
service aveksa_server restart
Related Articles
JavaScript error when trying to delete a certificate with special characters Number of Views What special characters are disallowed in Access Manager user and group names? Number of Views RSA Identity Governance and Lifecycle version 6.9.1 review does not accept the password with hash special character # Number of Views Special characters other than '_' and '$' are not allowed for Variables in Account Template Fields in RSA Identity Governa… Number of Views Special characters other than '_' and '$' are not allowed for Variables in AFX Connector Mapping Fields in RSA Identity Go… 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) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
