000036165 - After patching to RSA Identity Governance & Lifecycle 7.0.2 P03+, emails are not generated and sent due to the error 'Illegal hex characters in escape (%) pattern'

Document created by RSA Customer Support Employee on Apr 4, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036165
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2 P03+, 7.1.0
 
IssuePrior to RSA Identity Governance & Lifecycle 7.0.2 P03, emails with % on their email content were being generated and sent.
 
Email content with %
 


After patching to RSA Identity Governance and Lifecycle 7.0.2 P03 or higher patch versions, emails are not generated and sent due to the following error: 

Illegal hex characters in escape (%) pattern



You will find the error below in the aveksaServer.log, which can be downloaded by navigating to Admin > System > Server Nodes > aveksaServer.log :




03/12/2018 17:01:11.643 ERROR (Worker_actionq#Script Queue - Normal#WPDS_7057) [com.aveksa.server.workflow.scripts.nodes.SendEmailThread] Couldn't Send Email to due to: 
java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - For input string: "; " 
at java.net.URLDecoder.decode(URLDecoder.java:192) 
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.getBody(SendEmailThread.java:109) 
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.sendEmail(SendEmailThread.java:146) 
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.sendEmail(SendEmailThread.java:66) 
at com.aveksa.server.workflow.scripts.nodes.SendEmailNode.nodeAvailableAsynchronous(SendEmailNode.java:34) 
at com.aveksa.server.workflow.scripts.nodes.WorkflowNodeHandler.nodeAvailableAsynchronous(WorkflowNodeHandler.java:52
Cause The emails are not getting generated and sent if the email content has %. This is due to the message content was not encoded and saved for the Send Email node. 
ResolutionResolved on RSA Identity Governance & Lifecycle 7.0.2 P07 and 7.1.0 P01.
WorkaroundThe workaround is to either:
  • Replace the % character with %25 ,or
  • Remove it completely in the email content of the Send Email node.
You will find the email being sent correctly and no errors in the logs.

 
Character encoding

Attachments

    Outcomes