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

[Scott Cantor (Jira)]

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=eyJpIjoiZjExNjg2Y2JjODEzNDFiY2EwNTNkYmZmNWQyM2FjNzIiLCJwIjoiaiJ9 )

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

The Jira issue here is token authentication to the client registration endpoint. That means you have to get that token from the OP (either you, to give to the developer/app owner, or they get it themselves). These tokens don’t come from nothing, they have to be issued, so we have to create a new, properietary endpoint that issues them and rules and logic for how/when/whether to issue them.

It’s a bootstrap for token-based use of the registration endpoint.

With client registration itself, there is no token returned. The OP just returns a copy of the client metadata in the response as an echo of what it actually registered, in case it made any changes to it from policy. There’s no token returned there.

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

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/5db89003/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-1e4aa4cf-3bee-4ab4-a250-7ee209782075
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/5db89003/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-0d18ab5d-95a9-4bd5-81a6-384c06ba9542
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/5db89003/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-0ea22801-a6b1-437b-b216-566a1e4cd9ae
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/5db89003/attachment-0005.png>