Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-642

use of SchemaValidation metadata filter results in logged error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.1.1
    • Component/s: Configuration
    • Labels:
      None

      Description

      One of the things that was changed in v3.1.0 was that the shibboleth.SchemaBuilder bean was defined in system/conf/global-system.xml to fix IDP-559.

      The initial version of that bean definition was, I think, the same as our workround for 3.0.0:

      <bean id="shibboleth.SchemaBuilder"
         class="org.opensaml.saml.common.xml.SAMLSchemaBuilder" c:ver="SAML_11" />
      

      However, this was added to in order to address IDP-613 by injecting a net.shibboleth.utilities.java.support.xml.SchemaBuilder so that an extension schema can be included.

      That change seems to have been in error, however, as I now see the following error in logs if the schema validation filter is used:

      2015-03-12 12:30:51,902 - ERROR
          [net.shibboleth.utilities.java.support.xml.SchemaBuilder:275] -
          IO error adding schema from resource: ServletContext resource
          [/schema/shibboleth-metadata-1.0.xsd]
      java.io.FileNotFoundException: Could not open ServletContext resource
          [/schema/shibboleth-metadata-1.0.xsd] at org.springframework.web.context.support.ServletContextResource.getInputStream(ServletContextResource.java:141)
      

        Attachments

          Activity

            People

            Assignee:
            cantor.2@osu.edu Scott Cantor
            Reporter:
            ian@iay.org.uk Ian Young
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours, 10 minutes
                4h 10m