Description
Environment
Activity
Henri Mikkonen February 5, 2021 at 8:41 AM
Changed profile IDs from http://csc.fi/ns/profiles/* to http://shibboleth.net/ns/profiles/*
Henri Mikkonen January 29, 2021 at 11:30 AM
XML-namespaces are now changed with the following logic:
org.geant.idpextension.oidc.attribute.encoder -> urn:mace:shibboleth:2.0:resolver:oidc
org.geant.idpextension.oidc.attribute.filter -> urn:mace:shibboleth:2.0:afp:oidc
The resolver plugins were moved to the *java-oidc-common* library, see https://issues.shibboleth.net/jira/browse/JCOMOIDC-8.
Henri Mikkonen December 30, 2020 at 2:45 PM
The Java-files have now been repackaged into the net.shibboleth.idp.plugin.oidc.op and the references from XML-files have been updated. Unit tests are working, but testing with a real deployment is still needed.
TODO:
XML-namespaces (attribute resolver/filter plugins) still point to old org.geant.* ones.
Profile IDs contain http://csc.fi/ns/profiles/oidc -prefix
Henri Mikkonen November 13, 2020 at 11:42 AM
That would be ideal! Let's keep it in mind.
Rod Widdowson November 13, 2020 at 11:36 AM
Is there any value in noting that you might be able to continue to support (and deprecate-warn on) the legacy custom spring configuration name space?
We used this when we stripped the attribute filter and the attribute resolver of all their nonsense extra namespaces during the life of V3. It might make deployers's lives slightly easier
Something went wrong on our end
If this keeps happening, share this information with your admin, who should contact support.
Hash D3XM4T
Trace 8d6a2de4427945e88111090f5e3ef3f8
The configuration files and Java-code must not refer to the legacy namespaces. The common parts of the code should be moved into the OIDC-common project