SiteMinder : Access Gateway Unable to parse non English characters with "java.nio.charset.MalformedInputException"

Products

• SITEMINDER

Issue/Introduction

Issue Synopsis

Access gateway is unable to parse the non English characters in the users request while posting the non English characters data to backend application via Access gateway 

Access gateway WebAgent Trace Log

[10/24/2022][15:21:07][execute][][][][][2d22f437-20e50fb0-a70cfa16-639b16b1-a3f0d321-fc][][][][][Retrying to send the request to backend web server.Retry count: 3]
[10/24/2022][15:21:07][execute][][][][][2d22f437-20e50fb0-a70cfa16-639b16b1-a3f0d321-fc][][][][][Tried to send the request to backend web server three times.Throwing the exception to client. ]
[10/24/2022][15:21:07][Noodle::doGet][][][][][2d22f437-20e50fb0-a70cfa16-639b16b1-a3f0d321-fc][][][][][java.nio.charset.MalformedInputException: Input length = 1 at java.nio.charset.CoderResult.throwException(CoderResult.java:281)]
[10/24/2022][15:21:07][ErrorPageImpl::displayMessage][][][][][2d22f437-20e50fb0-a70cfa16-639b16b1-a3f0d321-fc][][][][][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][][][][][2d22f437-20e50fb0-a70cfa16-639b16b1-a3f0d321-fc][][][][][Leaving the agent.] 

Environment

Release : 12.8.x

Resolution

Follow below steps 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" ---) to be added 

For example: 

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 our noodle client uses while communicating with back end server.