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

[Nikolaus Ortner (JIRA)]

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

Nikolaus Ortner edited comment on SIDP-552 at 5/23/12 4:06 PM:
---------------------------------------------------------------

Tried the FilesystemMetadataProvider because it's the IdP's own metadata - no effect.
FileBackedHTTPMetadataProvider with URI https://localhost[:port]/idp/shibboleth did not work (system hung or some misconfiguration by me?).

Please see attached exception.txt - this happens when the metadata is requested the first time (manually via browser or some SP). This exception is not always thrown on subsequent calls.
..using the ResourceBackedMetadataProvider from the initial configuration (which seems to be ok, as I previousely mentioned).

      was (Author: nortner at fh-kaernten.at):
    Tried the FilesystemMetadataProvider because it's the IdP's own metadata - no effect.
FileBackedHTTPMetadataProvider with URI https://localhost[:port]/idp/shibboleth did not work (system hung or some misconfiguration by me?).

Please see attached exception.txt - this happens when the metadata is requested the first time (manually via browser or some SP). This exception is not thrown on subsequent calls.
..using the ResourceBackedMetadataProvider from the initial configuration (which seems to be ok, as I previousely mentioned).
  
> 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