metadata SchemaValidationFilter for OIDC metadata

[Paul B. Henson]

I'm testing out OIDC client configuration in metadata, but the schema
validation filter is barfing on it:

2023-11-07 18:31:11,560 - / - ERROR [org.opensaml.saml.metadata.resolver.filter.impl.SchemaValidationFilter:80] - Incoming metadata was not schema valid: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:oasis:names:tc:SAML:2.0:metadata":oidcOAuthRPExtensions}'. One of '{WC[##other:"urn:oasis:names:tc:SAML:2.0:metadata"]}' is expected.
2023-11-07 18:31:11,561 - / - ERROR [org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolver:551] - Metadata Resolver FilesystemMetadataResolver cpp-oidc: Error filtering metadata from /opt/shibboleth-idp/metadata/cpp-oidc.xml: Incoming metadata was not schema valid

I added the oidc ns to the file:

<EntitiesDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                    xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                    xmlns:oidcmd="urn:mace:shibboleth:metadata:oidc:1.0">


Does the schema validation filter not support oidc validation? Do I need
to download the xsd myself from

http://shibboleth.net/schema/oidc/saml-metadata-ext-oidcmd.xsd

and merge it as documented at

https://shibboleth.atlassian.net/wiki/spaces/IDP4/pages/1265631653/SchemaValidationFilter

?

Or do I just have something else broken and it should be working :).

Thanks...




-- 
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768