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

Henri Mikkonen (Jira) jira at shibboleth.atlassian.net
Tue Mar 15 08:05:51 UTC 2022


Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JOIDC-21 ( https://shibboleth.atlassian.net/browse/JOIDC-21?atlOrigin=eyJpIjoiOGIxOGE1NDg4YzYxNDEwNzg1NjgxNDA3ZmM4YjI1MmMiLCJwIjoiaiJ9 )

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

Added HTTP-Basic auth support for the CLI tool. This way the tool is still functional if the following property is set:

idp.oidc.issue-registration-access-token.authenticated = true
idp.oidc.issue-registration-access-token.accessPolicy = AccessByAdminUser

I tested the following policy to work as expected:

       <entry key="AccessByAdminUser">
           <bean parent="shibboleth.PredicateAccessControl">
               <constructor-arg>
                   <bean parent="shibboleth.Conditions.SubjectName" c:collection="#{'admin1'}" />
               </constructor-arg>
           </bean>
       </entry>

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

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:8522567 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/75f02ed3/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-7aa65917-9bd7-4c8d-9110-0a969f6eb04c
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/75f02ed3/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-50bacdee-8fe0-4971-94e5-5f0b1cc0d90b
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/75f02ed3/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-7139b72d-6a6b-4620-a915-78f4581b89f1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/75f02ed3/attachment-0005.png>


More information about the commits mailing list