[JIRA] (JOIDCRP-11) Client Identifier Resolution
Philip Smart (Jira)
jira at shibboleth.atlassian.net
Fri Mar 18 11:48:00 UTC 2022
Philip Smart ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=5afecdc1eb3ffa0c596652c4 ) *commented* on JOIDCRP-11 ( https://shibboleth.atlassian.net/browse/JOIDCRP-11?atlOrigin=eyJpIjoiZTlmZGFhM2UwMjc1NGNhMGFhMzBmMjY2NjZjYTAyZGYiLCJwIjoiaiJ9 )
Re: Client Identifier Resolution ( https://shibboleth.atlassian.net/browse/JOIDCRP-11?atlOrigin=eyJpIjoiZTlmZGFhM2UwMjc1NGNhMGFhMzBmMjY2NjZjYTAyZGYiLCJwIjoiaiJ9 )
Created a client_id resolver and reloadable service implementation. Uses a Storage Service backend, which by default is a simple map loaded from a user space XML file that maps between issuers and client_ids e.g.
<util:map id="shibboleth.authn.oidc.rp.IssuerToClientIdMap">
<entry key="https://www.certification.openid.net/test/a/test_rp_proxy/" value="mytestclient" />
</util:map>
This could be consolidated with the client authentication resolver, but as they are used in different parts of the flow, I have separated them for now. This is added to a OAuth2ClientContext which is then authoritative for the identifier of the client to use and key off in other lookups.
( https://shibboleth.atlassian.net/browse/JOIDCRP-11#add-comment?atlOrigin=eyJpIjoiZTlmZGFhM2UwMjc1NGNhMGFhMzBmMjY2NjZjYTAyZGYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDCRP-11#add-comment?atlOrigin=eyJpIjoiZTlmZGFhM2UwMjc1NGNhMGFhMzBmMjY2NjZjYTAyZGYiLCJwIjoiaiJ9 )
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:003460b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/59c2c9cd/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-82213ab2-f0c4-49a1-9233-077ab4dd1054
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/59c2c9cd/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-3df4830c-3f5c-4be0-a0c2-6bd423c8c6f8
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/59c2c9cd/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c0c8344b-3bb9-49e4-9439-fc9b96580157
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/59c2c9cd/attachment-0005.png>
More information about the commits
mailing list