|Applies To||RSA Product Set: Identity Governance & Lifecycle|
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.2 P04
|Issue||When sending emails or viewing the source of other forms, the charset is not always UTF-8 when using WildFly as an application server.|
In one example the email subject line was using ANSI_X3.4-1968; however the body of the email was using UTF-8.
|Cause||This issue is caused by the operating system environment having a default character set of ANSI_X3.4-1968, and since the application server did not specifically override the setting, the environment default was used.|
|Resolution||In WebSphere and Weblogic installations, a startup parameter is documented as being needed in the JVM startup arguments.|
This same JVM argument was not present in the WildFly application server startup script.
A fix was implemented for RSA Governance & Lifecycle with reference ID ACM-95236 which was addressed in these versions of RSA Identity Governance & Lifecycle and higher:
If you are below these versions and wish to manually workaround the issue prior to patching you should backup the existing file(s) in /etc/init.d/aveksa_server and /etc/init.d/aveksa_cluster
The instructions are the same for aveksa_server and aveksa_cluster
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.net.ssl.enableECC=false -Djava.awt.headless=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$AVEKSA_HOME $EXTRA_OPTS"
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"
service aveksa_server restart
This manual edit does not persist if the system is patched, and the patch is below the versions listed in the Resolution section. The manual edit would need to be reapplied after patches, upgrades, and hotfixes below those versions.