[JIRA] (JOIDC-7) Access token as JWT

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDC-7 ( https://shibboleth.atlassian.net/browse/JOIDC-7?atlOrigin=eyJpIjoiMTUzZjdiMjgzNWUzNDBkMjg2ZWM5OThlYzAwNDU2MDYiLCJwIjoiaiJ9 )

Re: Access token as JWT ( https://shibboleth.atlassian.net/browse/JOIDC-7?atlOrigin=eyJpIjoiMTUzZjdiMjgzNWUzNDBkMjg2ZWM5OThlYzAwNDU2MDYiLCJwIjoiaiJ9 )

This is implemented save for encryption support. Debugger verifies that the outbound message context does not contain any of the OIDC/SAML metadata contexts, so this is a plausible location to use for the second set of metadata needed for the resource server. The existing encryption actions can hopefully be wired to locate the metadata there instead of the inbound side, or will need minor enhancement to do so.

We will need policy for whether to continue issuing tokens in the absence of metadata (and thus an encryption key) for the resource server, i.e. the token audience. A defaulted but pluggable function that returns the first audience should be sufficient to decide which client to encrypt to.

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

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#100190- sha1:4ce3a7c )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220203/36969fb8/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-c92399d9-d3e4-4253-b233-166ea495d8db
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220203/36969fb8/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-14a4d312-98f2-49ff-8544-02372cdbe2b6
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220203/36969fb8/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-a4846186-d4b3-475e-b961-1167e848c65b
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220203/36969fb8/attachment-0005.png>