Error with SPs registered with InCommon

Ramaiah, Vanna G. ramaiah at musc.edu
Wed Feb 19 01:21:59 UTC 2025


It looks like InCommon made a change to validity interval that caused the issue. To switch to mdq,


  1.  Added the metadata provider in metadataproviders.xml. Added the cert in credentials folder.
  2.  There is nothing grouped for incommon service providers in attribute-filter.xml. Attributes are passed to each service provider separately. Do I need to modify anything else?
  3.  After adding the mdq metadata provider, is it safe to remove the provider from md.incommon.org?

<MetadataProvider id="incommonmdq"
                  xsi:type="DynamicHTTPMetadataProvider"
                  maxCacheDuration="PT24H"
                  minCacheDuration="PT10M">
        <MetadataFilter xsi:type="SignatureValidation"  requireSignedRoot="true" certificateFile="%{idp.home}/credentials/inc-md-cert-mdq.pem" />
        <MetadataFilter xsi:type="RequiredValidUntil" maxValidityInterval="P14D" />
        <MetadataFilter xsi:type="EntityAttributes">
                <saml:Attribute Name="source_of_metadata">
                            <saml:AttributeValue>incommon-mdq</saml:AttributeValue>
                </saml:Attribute>
                <ConditionRef>shibboleth.Conditions.TRUE</ConditionRef> </MetadataFilter>
        <MetadataQueryProtocol>https://mdq.incommon.org/</MetadataQueryProtocol<https://mdq.incommon.org/%3c/MetadataQueryProtocol>>
        </MetadataProvider>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250219/cff3ba71/attachment.htm>


More information about the users mailing list