OpenID Provider (OP) and Relying Party (RP) enforcer-data overrides
Key details
Basics
Logistics
Basics
Logistics
Description
Both OP V3.4.0 and RP V1.0.0 are built against the enforcer-data V1.0.13 using a property override in their parent POMs.
The reason for this:
'I realised that oidc-config was deploying into net.shibboleth.idp.oidc in Nexus, which was just a weird place for it to exist (nestled on its own amongst the IdP modules). So I changed it to net.shibboleth.idp.plugin.config.oidc so it went into its own plugin group. I then deployed it. Of course then the OP (RP would also) failed the enforcer checks because it does not have a keyring for that.So I will need to update enforcer-data and release it. We will then need to override the enforcer-data version for this release and test that works. Probably best to avoid a parent release if possible.'
Both OP V3.4.0 and RP V1.0.0 are built against the enforcer-data V1.0.13 using a property override in their parent POMs.
The reason for this:
'I realised that oidc-config was deploying into
net.shibboleth.idp.oidcin Nexus, which was just a weird place for it to exist (nestled on its own amongst the IdP modules). So I changed it tonet.shibboleth.idp.plugin.config.oidcso it went into its own plugin group. I then deployed it. Of course then the OP (RP would also) failed the enforcer checks because it does not have a keyring for that.So I will need to update enforcer-data and release it. We will then need to override the enforcer-data version for this release and test that works. Probably best to avoid a parent release if possible.'