[JIRA] (JOIDC-11) Support for client_credentials grant
Scott Cantor (Jira)
jira at shibboleth.atlassian.net
Tue Nov 9 19:26:54 UTC 2021
Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDC-11 ( https://shibboleth.atlassian.net/browse/JOIDC-11?atlOrigin=eyJpIjoiZGIzYjZlNGVmOWE5NGY3NjkxOGZkMGYzZDkxNGIwZDkiLCJwIjoiaiJ9 )
Re: Support for client_credentials grant ( https://shibboleth.atlassian.net/browse/JOIDC-11?atlOrigin=eyJpIjoiZGIzYjZlNGVmOWE5NGY3NjkxOGZkMGYzZDkxNGIwZDkiLCJwIjoiaiJ9 )
We have to support JWT for various reasons. I had expressed some feelings that we might consider dumping support for opaque tokens but there’s no real drive to do that. But I wasn’t really planning on trying to support them explicitly for new use cases unless there’s a clear reason to do it. The only reason I can think of is confidentiality of claims, and encryption should handle that.
We do have to support introspection, we’re not expecting the client to understand the format if it doesn’t want to.
The RFC doesn’t appear to require a scope claim, it only includes a lot of non-productive hand wringing about how to deal with scope, aud, sub, etc. that amount to “do the right things but we don’t know what they are and if you do the wrong things it’s dangerous”. I think we just need to treat all that as garbage in, garbage out and stay out of it, just supply some basic defaults and assume a deployer implemented set of rules. If it’s not a MUST, we’re not going to mandate it.
( https://shibboleth.atlassian.net/browse/JOIDC-11#add-comment?atlOrigin=eyJpIjoiZGIzYjZlNGVmOWE5NGY3NjkxOGZkMGYzZDkxNGIwZDkiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-11#add-comment?atlOrigin=eyJpIjoiZGIzYjZlNGVmOWE5NGY3NjkxOGZkMGYzZDkxNGIwZDkiLCJwIjoiaiJ9 )
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:d14df9b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211109/03ead333/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-1bf58a53-f9bf-47b1-b092-fb120ca444b5
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211109/03ead333/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-67184668-1911-4ec6-8513-308fbcc9ac68
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211109/03ead333/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-0c54d6c0-a8ef-4471-916b-5cb7af39f3a5
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211109/03ead333/attachment-0005.png>
More information about the commits
mailing list