000037348 - Special characters in email subject lines do not display as expected in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Apr 15, 2019•Last modified by RSA Customer Support Employee on Feb 14, 2020
Version 4Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000037348
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1
Platform: WildFly
 
IssueWhen viewing emails sent via RSA Identity Governance & Lifecycle installed on a WildFly application server, special characters that display correctly in the body of the email do not display correctly in the subject line of the email.
 
CauseThis issue occurs when the character set is not using UTF-8. For example, in this case the email subject line was using ANSI_X3.4-1968 but the body of the email was using UTF-8.

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.
 
ResolutionThis issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
  • 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.



  1. Login to the WildFly application server as the root user.
  2. Backup the existing startup file: 


cp /etc/init.d/aveksa_server /etc/init.d/aveksa_server_backup


  1. Edit the startup file:


vi /etc/init.d/aveksa_server


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


 

Attachments

    Outcomes