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

[Pierre Sagne (Jira)]

Pierre Sagne ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3Ab389f93c-082f-42b2-8684-ac3e951ab163 ) *commented* on JOIDC-155 ( https://shibboleth.atlassian.net/browse/JOIDC-155?atlOrigin=eyJpIjoiYTIyMWZiNDdiODM4NDlkZWEyMjc5N2MwNWY3MWZhMjUiLCJwIjoiaiJ9 )

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

The resource defaulting to the audience in the metadata would actually be great, and would fix my problem and go beyond that, because it is not always well known by clients which resources have to introspect their token.

Maybe adding a boolean parameter in the SSO profile, which automatically adds metadata audiences as resources, and if you are reluctant to do this without checking anything, maybe add a way to add this to the consent page (but that’s just an idea, my use cases really don't care about having this in consent page)

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

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:b79b7f6 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230509/9c9cb71b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-52d66b8e-c110-480e-adc7-c418fd8718b4
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230509/9c9cb71b/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-b071b1cb-2e84-4637-9805-325fa61ac4d1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230509/9c9cb71b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-e624ed8e-239f-4bb4-86d3-3aa9ec728efe
Type: image/png
Size: 296 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230509/9c9cb71b/attachment-0005.png>