[JIRA] (JCOMOIDC-23) Add OpenID Provider Configuration Document Resolver

[Philip Smart (Jira)]

Philip Smart ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=5afecdc1eb3ffa0c596652c4 ) *commented* on JCOMOIDC-23 ( https://shibboleth.atlassian.net/browse/JCOMOIDC-23?atlOrigin=eyJpIjoiNWQ4NjhmMjQxMzJlNDE1YjgxYTUyZWM4NTJkM2E3OTUiLCJwIjoiaiJ9 )

Re: Add OpenID Provider Configuration Document Resolver ( https://shibboleth.atlassian.net/browse/JCOMOIDC-23?atlOrigin=eyJpIjoiNWQ4NjhmMjQxMzJlNDE1YjgxYTUyZWM4NTJkM2E3OTUiLCJwIjoiaiJ9 )

Split metadata cache into both a dynamic and batch version.

* Also, split backing store to dynamic and batch (similar to original).
* The Batch version is (as before) a complete cache reload from a synchronized background scheduled task - compared to the individual metadata in-flight update model of the dynamic cache.
* Neither feature-complete with existing SAML resolver, not so much of an issue for the OIDC use case, but still.

The spring factory creates one or the other type (batch v dynamic) based on the configured properties/strategies. Not clear if using a spring factory is the best for that, especially given some of the generic types - will test that.

( https://shibboleth.atlassian.net/browse/JCOMOIDC-23#add-comment?atlOrigin=eyJpIjoiNWQ4NjhmMjQxMzJlNDE1YjgxYTUyZWM4NTJkM2E3OTUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JCOMOIDC-23#add-comment?atlOrigin=eyJpIjoiNWQ4NjhmMjQxMzJlNDE1YjgxYTUyZWM4NTJkM2E3OTUiLCJwIjoiaiJ9 )

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#100183- sha1:445115c )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211014/cfac88f7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-a91aedcd-0292-474f-af94-0575a5e15090
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211014/cfac88f7/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-05b2d618-3e90-4a88-b025-e9f955ca839f
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211014/cfac88f7/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-33516724-567b-45d3-9df0-4bde3ecb0ce4
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211014/cfac88f7/attachment-0005.png>