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

[Keith Wessel (Jira)]

Keith Wessel ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=60ad392bb4624d00692388ed ) *commented* on JOIDC-21 ( https://shibboleth.atlassian.net/browse/JOIDC-21?atlOrigin=eyJpIjoiNzVmODA0ZDcxYjVhNDc3YzkxNTM1ZTk2ZDU4YzAzM2UiLCJwIjoiaiJ9 )

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

I wasn’t talking about the token issuing endpoint, though. I was just taling about client registration… the first step. Anything we’ve done here wtih dynamic client registration, the client gets back the generated token in the response from the registration call. They haven’t needed to call a token issuing endpoint to get the generated token. Either there are two ways to get the token, one of which I wasn’t aware of, or we’re not on the same page at all. What token does the token issuing endpoint issue? Lots of tokens in OIDC, I want to make sure I know what token you’re talking about.

If developers need some type of barer token before they can register a client, and if I either have to issue that barer token externally or Shibboleth issues it but I know who authenticated to get it, then yes, we’re good here.

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

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/fef7756c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-5d45ab21-2e01-4ab6-9702-b97d0870efc6
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/fef7756c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-4739f3f0-6a29-41e0-8252-1135f8a48d53
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/fef7756c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-125da1fa-e855-478c-b2ae-26b53758cf4d
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/fef7756c/attachment-0005.png>