[JIRA] (JOIDC-153) Attribute recipient grouping ID is not set in the token and userinfo flows

[Henri Mikkonen (Jira)]

Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *created* an issue

IdP Plugin - OIDC OP ( https://shibboleth.atlassian.net/browse/JOIDC?atlOrigin=eyJpIjoiMmUyNjc3ZTc5ZjcwNGRiZTg3ZTdmMDNiODc3NzMxYWYiLCJwIjoiaiJ9 ) / Bug ( https://shibboleth.atlassian.net/browse/JOIDC-153?atlOrigin=eyJpIjoiMmUyNjc3ZTc5ZjcwNGRiZTg3ZTdmMDNiODc3NzMxYWYiLCJwIjoiaiJ9 ) JOIDC-153 ( https://shibboleth.atlassian.net/browse/JOIDC-153?atlOrigin=eyJpIjoiMmUyNjc3ZTc5ZjcwNGRiZTg3ZTdmMDNiODc3NzMxYWYiLCJwIjoiaiJ9 ) Attribute recipient grouping ID is not set in the token and userinfo flows ( https://shibboleth.atlassian.net/browse/JOIDC-153?atlOrigin=eyJpIjoiMmUyNjc3ZTc5ZjcwNGRiZTg3ZTdmMDNiODc3NzMxYWYiLCJwIjoiaiJ9 )

Issue Type: Bug Assignee: Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) Components: Token Endpoint, UserInfo Endpoint Created: 27/Apr/23 7:53 AM Fix Versions: 3.4.0 Priority: Trivial Reporter: Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd )

In OIDC sequences, the attribute resolution and filtering may be performed in all authorize, token and userinfo flows/endpoints. Currently only authorize-flow sets the recipient grouping ID (see SWF action SetSectorIdentifierForAttributeResolution , it calls AttributeResolutionContext.setAttributeRecipientGroupID(..) ).

All the flows should set it with the same logic.

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

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#100223- sha1:02266b8 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/da47d2db/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-7da3361c-c4ee-4ae0-b64a-b26495faca84
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/da47d2db/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-trivial-0e56b6e1-34db-4df3-9c41-079bdd0e2551
Type: image/png
Size: 446 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/da47d2db/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-527cac40-c242-4105-ad06-19e167633541
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/da47d2db/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-269d6448-c2c7-4bfa-80b0-6b98c16a3e07
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/da47d2db/attachment-0007.png>