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

Tue May 22 16:44:03 BST 2012

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

Nikolaus Ortner commented on IDP-171:
-------------------------------------

Sorry - messed up the projects (should have been "Shibboleth IdP 2 - Java").
And my first impression was wrong - ResourceBackedMetadataProvider doesn't make the problem. Seems like IdP's own Metadata is (additionally) loaded per ProfileHandler (conf/handler.xml).

> IdP-Metadata containing german umlauts shows encoding-problems on Microsoft Windows (Error in ResourceBackedMetadataProvider?)
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IDP-171
>                 URL: https://issues.shibboleth.net/jira/browse/IDP-171
>             Project: Identity Provider
>          Issue Type: Bug
>          Components: Metadata
>         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
>
> 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