SiteMInder : Unable to parse non English characters in CA Access Gateway (SPS) : java.nio.charset.MalformedInputException: Input length = 1

Products

• SITEMINDER

Issue/Introduction

The CA Access Gateway (SPS) is unable to parse the non-English characters in the users' request while posting the non-English characters data to the backend application.

SPS Agent log:

[10/24/2022][15:21:07][execute][][][][][][][][][][Retrying to send the request to backend web server.Retry count: 3]
[10/24/2022][15:21:07][execute][][][][][][][][][][Tried to send the request to backend web server three times.Throwing the exception to client. ]
[10/24/2022][15:21:07][Noodle::doGet][][][][][][][][][][java.nio.charset.MalformedInputException: Input length = 1 at java.nio.charset.CoderResult.throwException(CoderResult.java:281)]
[10/24/2022][15:21:07][ErrorPageImpl::displayMessage][][][][][][][][][][Custom Error Pages : Custom message is not an URL. If URL is specified then it might not be in proper format. Considering it as plain text message.]
[10/24/2022][15:21:07][ProxyValve::invoke][][][][][][][][][][Leaving the agent.] 

Resolution

Follow the steps below to parse the non-English characters.

Navigate to (sps_home)\proxy-engine\conf and open the SmSpsProxyEngine.properties file: 

• Add the following in the NETE_SPS_PROXYENGINE_CMD section before the classpath: 
  

  -Dhttp_protocol_element_charset="UTF-8"

For instance:

NETE_SPS_PROXYENGINE_CMD="%NETE_SPS_JAVA_HOME%\bin\java.exe" -Xms512m -Xmx1024m -XX:MaxMetaspaceSize=256M -Dhttp_protocol_element_charset="UTF-8" 

Note:

Here UTF-8 is the character set that the CA Access Gateway (SPS) noodle client uses while communicating with the back end server.