[JIRA] (JOIDC-21) Use token authentication for OIDC dynamic client registration

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Thu Mar 10 20:02:53 UTC 2022


Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDC-21 ( https://shibboleth.atlassian.net/browse/JOIDC-21?atlOrigin=eyJpIjoiYjA3MTk3Yzc4N2JlNGVmMzhiODEwOGQ1ZmQyMjVlZWIiLCJwIjoiaiJ9 )

Re: Use token authentication for OIDC dynamic client registration ( https://shibboleth.atlassian.net/browse/JOIDC-21?atlOrigin=eyJpIjoiYjA3MTk3Yzc4N2JlNGVmMzhiODEwOGQ1ZmQyMjVlZWIiLCJwIjoiaiJ9 )

I guess that’s an option we could have pursued, but it seemed silly to do that when we already issue securable access tokens elsewhere for the OP’s consumption. The devil is in the details of what can end up in the tokens relative to who’s asking. When it’s the operator asking, anything is probably fine, but once we open it to developers asking, obviously that means controls so I’m trying to limit what gets in the tokens anywhere I can.

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

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#100197- sha1:b6de2d8 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/ccd3501a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-88c3225d-51f7-48c6-8d18-7ab0a9abaae0
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/ccd3501a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-f9fd9431-0dab-453c-a3cf-f42f6807d138
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/ccd3501a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-fc3ca079-0abf-48a3-b760-abc20cdf7752
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/ccd3501a/attachment-0005.png>


More information about the commits mailing list