You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2014/05/27 18:34:01 UTC

[jira] [Updated] (FEDIZ-79) Encoding of SignInResponse configurable

     [ https://issues.apache.org/jira/browse/FEDIZ-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated FEDIZ-79:
-------------------------------------

    Fix Version/s: 1.2.0
                   1.1.1

> Encoding of SignInResponse configurable
> ---------------------------------------
>
>                 Key: FEDIZ-79
>                 URL: https://issues.apache.org/jira/browse/FEDIZ-79
>             Project: CXF-Fediz
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 1.1.0, 1.0.3, 1.2.0
>            Reporter: Oliver Wulff
>            Assignee: Oliver Wulff
>             Fix For: 1.1.1, 1.2.0
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.2#6252)