[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=eyJpIjoiNDMxMjVkYWVjZTZlNDQ3NDg2M2QxZjgxYmViMTk0Y2QiLCJwIjoiaiJ9 )

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

I’ve thought all along that this registration endpoint could be used by developers, not just the IdP operator. That, in fact, is my desire, at least until we get a pointy-clicky OIDC registration interface similar to our SAML registration interface. But even then, we might keep it around longer. Right now, though, that means I’ve got a dynamic client registration endpoint that’s only limited (externally in Tomcat) by what client IPs can use it. So, the need for the out-of-band registered barer token is pretty obvious. The friendly naem for the barer token isn’t to provide contact info in the registered OIDC metadata. It’s more so I know who the barer token belongs to for internal tracking. It also allows the registrant to use different contacts as apropriate while still allowing me with a trail back to who registered it. If it was registered using barer token x, and I know barer token X was issued to John Smith, then unless John is sharing his token, I know he registered it.

The real desire is the out-of-band issued barer token that’s required for authentication before dynamically registering a client. The friendly name was just a “this would be nice while we’re at it.” Honestly, if I’ve got a web form or some other similar process for issuing barer tokens and making them known to Shibboleth, I could do my own storage of who the token belongs to elsewhere.

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

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/2a80aa1d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-5abcdf5d-fbec-4599-aa9d-b54cb8224a3e
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/2a80aa1d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-2236b97e-3976-496b-b179-2da7ed98a1d5
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/2a80aa1d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-32bc0a02-700c-4edd-a82b-1e25eb965332
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220310/2a80aa1d/attachment-0005.png>