[JIRA] (JCOMOIDC-29) Consider adjustments to OIDC/OAuth profile configs
Scott Cantor (Jira)
jira at shibboleth.atlassian.net
Thu Dec 9 01:00:46 UTC 2021
Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JCOMOIDC-29 ( https://shibboleth.atlassian.net/browse/JCOMOIDC-29?atlOrigin=eyJpIjoiYjFlOTNjM2ZmZTU5NGU4M2EwYTRmNGQ3ZWNhOWEzODIiLCJwIjoiaiJ9 )
Re: Consider adjustments to OIDC/OAuth profile configs ( https://shibboleth.atlassian.net/browse/JCOMOIDC-29?atlOrigin=eyJpIjoiYjFlOTNjM2ZmZTU5NGU4M2EwYTRmNGQ3ZWNhOWEzODIiLCJwIjoiaiJ9 )
Mostly just made some cosmetic adjustments adding an OAuth2 marker interface for the two existing “pure” OAuth endpoints.
Most of the existing profiles appear to be at least nominally OIDC “enriched”. One possible exception is the keyset publishing endpoint, that probably isn’t.
I renamed the “OIDCCoreProtocol” class to OIDCAuthorization and added an OIDCToken class that’s just an empty subclass of that one for now, so a duplicate for the moment.
The work now would be to figure out what, if anything, is only relevant to the front or back channels only, but I’m not sure given the OAuth design that anything actually is. If that’s the case, it may be rare to need to actually supply a Token profile bean unless doing the pure OAuth work we’re extending this to handle.
( https://shibboleth.atlassian.net/browse/JCOMOIDC-29#add-comment?atlOrigin=eyJpIjoiYjFlOTNjM2ZmZTU5NGU4M2EwYTRmNGQ3ZWNhOWEzODIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JCOMOIDC-29#add-comment?atlOrigin=eyJpIjoiYjFlOTNjM2ZmZTU5NGU4M2EwYTRmNGQ3ZWNhOWEzODIiLCJwIjoiaiJ9 )
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:f6eba4b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211209/6ed77bdc/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-65b177cf-aacc-42c8-8dba-d025e3965fe0
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211209/6ed77bdc/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-af7593eb-c267-4ee6-8775-3ac8d0550e21
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211209/6ed77bdc/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-16630150-6bc3-4044-a377-6f47a683e1de
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211209/6ed77bdc/attachment-0005.png>
More information about the commits
mailing list