shibd error

[Goldberg, Arthur P]

Hello Shib Users

I continue my effort to configure an Apache / Shibbolith SO that’s using an Azure IdP.

The shibd consistently reports a “Shibboleth.LogoutInitiator.SAML2 : error building MessageEncoder: Unknown plugin type.” error. Googling and searching the Shibbolith SO 3 documentation doesn’t seem to be helpful. This error occurs in the following log stream:

    2021-05-21 10:56:01 INFO Shibboleth.Application : adding LogoutInitiator of type (SAML2) to chain (/Logout)
    2021-05-21 10:56:01 INFO Shibboleth.Application : auto-configuring Logout endpoints for protocol (SAML2)
    2021-05-21 10:56:01 INFO Shibboleth.Application : adding SingleLogoutService for Binding (urn:oasis:names:tc:SAML:2.0:bindings:SOAP) at (/SLO/SOAP)
    2021-05-21 10:56:01 INFO Shibboleth.Application : adding SingleLogoutService for Binding (urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect) at (/SLO/Redirect)
    2021-05-21 10:56:01 INFO Shibboleth.Application : adding SingleLogoutService for Binding (urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST) at (/SLO/POST)
    2021-05-21 10:56:01 INFO Shibboleth.Application : adding SingleLogoutService for Binding (urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact) at (/SLO/Artifact)
    2021-05-21 10:56:01 ERROR Shibboleth.LogoutInitiator.SAML2 : error building MessageEncoder: Unknown plugin type.
    2021-05-21 10:56:01 INFO Shibboleth.Handler.DiscoveryFeed : feed files will be cached in /data/shibds/discofeed
    2021-05-21 10:56:01 INFO Shibboleth.Application : building MetadataProvider of type XML...
    2021-05-21 10:56:01 INFO OpenSAML.MetadataProvider.XML : loaded XML resource (/etc/shibboleth/AzureIdPMetadata.xml)
    2021-05-21 10:56:01 INFO Shibboleth.Application : no TrustEngine specified or installed, using default of ExplicitKey
    2021-05-21 10:56:01 INFO Shibboleth.Application : building AttributeExtractor of type XML...
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : loaded XML resource (/etc/shibboleth/attribute-map.xml)
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oasis:names:tc:SAML:attribute:subject-id
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oasis:names:tc:SAML:attribute:pairwise-id
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oid:1.3.6.1.4.1.5923.1.1.1.6
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:mace:dir:attribute-def:eduPersonPrincipalName
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oid:1.3.6.1.4.1.5923.1.1.1.9
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:mace:dir:attribute-def:eduPersonScopedAffiliation
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oid:1.3.6.1.4.1.5923.1.1.1.7
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:mace:dir:attribute-def:eduPersonEntitlement
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oid:1.3.6.1.4.1.5923.1.1.1.10
    2021-05-21 10:56:01 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

In addition, the Network developer tool in the Chrome browser accessing the site using the SO reports a “Cross-Origin Resource Sharing error: PreflightMissingAllowOriginHeader”. I can share a screenshot with anyone who’s interested.

How do you recommend I address this problem? What additional configuration or logging data would be helpful?

Thanks
Arthur

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