[JIRA] Commented: (SIDP-552) IdP-Metadata containing german umlauts shows encoding-problems on Microsoft Windows (Error in ResourceBackedMetadataProvider?)

[Chad La Joie (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SIDP-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096#comment-14096 ] 

Chad La Joie commented on SIDP-552:
-----------------------------------

So, there are various things going on here.  First, the IdP is reading the content in just fine.  It's the exact same code as is used elsewhere in the IdP.  Second the IdP is writing the metadata out to the response.  That uses the same code as is used to write out all the SAML messages which also works fine.  Next the container is taking the written out byte[] and doing whatever it does with it.  So, have you checked you container configuration to see what sort of encoding it is performing by default?

> IdP-Metadata containing german umlauts shows encoding-problems on Microsoft Windows (Error in ResourceBackedMetadataProvider?)
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SIDP-552
>                 URL: https://issues.shibboleth.net/jira/browse/SIDP-552
>             Project: Shibboleth IdP 2 - Java
>          Issue Type: Bug
>         Environment: IdP 2.3.6 (MSI-Install) on Microsoft Windows Server 2008 (x86 SP 2 and 64 Bit R2 SP1, Sun/Oracle JRE 1.6.0_31-b05 / 1.6.0_29-b11). IdP runs standalone with the included Tomcat 6.
>            Reporter: Nikolaus Ortner
>            Assignee: Chad La Joie
>            Priority: Minor
>         Attachments: exception.txt
>
>
> Had some trouble with german umlauts in our IdP-Metadata (OrganizationName, OrganizationDisplayName and UIInfo/DisplayName). I tried various encodings in the XML declaration besides <?xml version="1.0" encoding="UTF-8"?> and saving the file in different encodings (UTF-8/ANSI/..) - but no combination did work. MetadataProvider [id="IdPMD"] is of type "ResourceBackedMetadataProvider".
> The workaround was to start tomcat's Java with Option "-Dfile.encoding=UTF8" [side-effects on other applications may occur then?] and the specified encoding is then taken into account. It works fine with ISO-8859-1 encoded metadata now.
> Since other configuration files are always read correct according to their specified encoding (eg. conf/attribute-resolver.xml where I have some static attributes containing umlauts in their values), it seems like the ResourceBackedMetadataProvider has a problem.
> -Niko

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira