[JIRA] (JOIDCRP-7) OIDC login flow - metadata use/mgmt
Scott Cantor (Jira)
jira at shibboleth.atlassian.net
Thu Feb 17 15:49:34 UTC 2022
Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDCRP-7 ( https://shibboleth.atlassian.net/browse/JOIDCRP-7?atlOrigin=eyJpIjoiYTNmM2RjNDc5NmU5NGMxZjlkODgxM2QxZGNlOTEyYzkiLCJwIjoiaiJ9 )
Re: OIDC login flow - metadata use/mgmt ( https://shibboleth.atlassian.net/browse/JOIDCRP-7?atlOrigin=eyJpIjoiYTNmM2RjNDc5NmU5NGMxZjlkODgxM2QxZGNlOTEyYzkiLCJwIjoiaiJ9 )
Yes, whatever I was originally thinking about here 3 years ago!, it’s clear to me now that the way we want this to work with respect keys is via a CredentialResolver
In SAML, we have org.opensaml.saml.security.impl.MetadataCredentialResolver to do this. If we don’t already have this for OIDC, we just need to build that too. I know there’s a separate component to do the JWKS caching, so we’d just inject that into it and the credential resolver would just hide all that detail. Once you have that, and a TrustEngine, you inject it into the TrustEngine to take care of things.
( https://shibboleth.atlassian.net/browse/JOIDCRP-7#add-comment?atlOrigin=eyJpIjoiYTNmM2RjNDc5NmU5NGMxZjlkODgxM2QxZGNlOTEyYzkiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDCRP-7#add-comment?atlOrigin=eyJpIjoiYTNmM2RjNDc5NmU5NGMxZjlkODgxM2QxZGNlOTEyYzkiLCJwIjoiaiJ9 )
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#100192- sha1:e250074 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/395f7b7a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-93b9ad38-8ac9-4988-8b29-0bb6ad9164a7
Type: image/png
Size: 452 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/395f7b7a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-35f94d80-a454-4990-8e00-368eb8fcc7bd
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/395f7b7a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-3905b323-e1f9-41a4-9e7d-91ac82858cef
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/395f7b7a/attachment-0005.png>
More information about the commits
mailing list