Details
Description
The SignInResponse is read with the encoding of the underlying JVM which can cause issues if special characters are present in the SAML token (ex. German umlaut).
The encoding should be configurable for the SignInResponse only.
This affects the Tomcat, Jetty and Websphere plugin but not the Spring plugin as the Spring CharacterEncodingFilter (http://docs.spring.io/spring/docs/3.0.x/api/org/springframework/web/filter/CharacterEncodingFilter.html) can be configured in the web.xml
Attachments
Issue Links
- relates to
-
FEDIZ-120 IDP Encoding of SignInResponse configurable
-
- Closed
-