[JIRA] (JOIDC-155) Documentation lacks clear description of interaction between introspection and audience

[Scott Cantor (Jira)]

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

Re: Documentation lacks clear description of interaction between introspection and audience ( https://shibboleth.atlassian.net/browse/JOIDC-155?atlOrigin=eyJpIjoiNTJiMmVlODRmNjdjNDgwNDg4MTZjZGFmNDQ2YjVjZjciLCJwIjoiaiJ9 )

I haven’t reviewed exhaustively but it’s my best guess that it does require that the client_id has to match the audience/resource value, I don’t see any indirection mechanism.

The only workaround I can see for that is the defaulting. I think it’s possible to add the resource server’s client_id as an audience in the original client’s metadata and have it serve as a “default” audience to use when there’s no resource parameter. If true, there’d never be a resource parameter hitting the wire to trip the Nimbus code, and none of our code enforces this so far as I know.

So that’s a workaround but not a solution in the general sense.

I don’t know how much appetite we have to support bad client_id approaches when it’s a lot of work and I suspect this would take a lot of work to code around. We’d have to extend the metadata with some kind of indirection that allows for a secondary lookup of the resource server URI. We have precedent for that in CAS and SAML Artifact support, so it’s possible, but that’s definitely some work.

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

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#100225- sha1:7f918b6 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230505/99d1d4aa/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-af2c4761-a795-4ff6-9428-9d10bd9713a4
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230505/99d1d4aa/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-901b1596-587b-4830-8d26-6e9644482bdb
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230505/99d1d4aa/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c7fab389-c1f1-448e-934b-34db8b4e9eb8
Type: image/png
Size: 296 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230505/99d1d4aa/attachment-0005.png>