[JIRA] (JOIDC-61) Support metadata policies in the dyn. reg. profile configuration

[Henri Mikkonen (Jira)]

Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JOIDC-61 ( https://shibboleth.atlassian.net/browse/JOIDC-61?atlOrigin=eyJpIjoiZjA3YThiNzQ3MmIzNGFiNjhlZmM0NWQxYzk1ZWFjMDUiLCJwIjoiaiJ9 )

Re: Support metadata policies in the dyn. reg. profile configuration ( https://shibboleth.atlassian.net/browse/JOIDC-61?atlOrigin=eyJpIjoiZjA3YThiNzQ3MmIzNGFiNjhlZmM0NWQxYzk1ZWFjMDUiLCJwIjoiaiJ9 )

Initial (still incomplete) support for metadata policies added. Two new properties related to this feature:

* *idp.oidc.dynreg.defaultMetadataPolicyFile* : a full path to a file containing the default metadata policy in JSON
* *idp.oidc.dynreg.defaultMetadataPolicy* : a bean to define the default metadata policy (Map<String, MetadataPolicy>)

Some remarks / TODOs:

* RegistrationClaimsSet overlaps with the other classes for claims sets in the same package, but is still independent.
* ValidateRegistrationRequestMetadata only validated the incoming request metadata against the policy, but it doesn’t store the enforced metadata anywhere yet.
* Default metadata policy resolver (via file) doesn’t handle non-existing files yet: flow tests work as test file exists, but real deployment doesn’t.
* Consider adding some interfaces / types / engines in order to have this complicated function-signatures:

* 
Function<Pair<Map<String, MetadataPolicy>, Map<String, MetadataPolicy>>, Pair<Map<String, MetadataPolicy>, Boolean>> metadataPolicyMergingStrategy;

( https://shibboleth.atlassian.net/browse/JOIDC-61#add-comment?atlOrigin=eyJpIjoiZjA3YThiNzQ3MmIzNGFiNjhlZmM0NWQxYzk1ZWFjMDUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-61#add-comment?atlOrigin=eyJpIjoiZjA3YThiNzQ3MmIzNGFiNjhlZmM0NWQxYzk1ZWFjMDUiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100187- sha1:07b4f58 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220107/32643633/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-aaf75453-2112-4100-85ef-14f89f799940
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220107/32643633/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-08f02f55-71fa-430f-a9bf-f8c4e56553fe
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220107/32643633/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-5ce863df-2bd4-4673-9c80-fd34c70e9e1f
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220107/32643633/attachment-0005.png>