000037348 - Email subject and other variables are using a charset other than UTF-8 which causes undesired display or errors in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Apr 15, 2019Last modified by RSA Customer Support Employee on Apr 15, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000037348
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.2 P04
 
IssueWhen 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.
CauseThis 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.
ResolutionIn 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:
  • 7.0.2 P14
  • 7.1.0 P07
  • 7.1.1 P02
  • 7.1.2


 
Workaround

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
  1. vi the script within /etc/init.d.
  2. 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"


  1. 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"


  1. Save the edits. 

:wq!


  1. 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


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.

Attachments

    Outcomes