[JIRA] (IDP-1919) CAS validation flows don't run consent checking interceptor
Clemens Bergmann (Jira)
jira at shibboleth.atlassian.net
Tue Mar 15 09:10:57 UTC 2022
Clemens Bergmann ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=617bb50a5800630069a5b0f0 ) *commented* on IDP-1919 ( https://shibboleth.atlassian.net/browse/IDP-1919?atlOrigin=eyJpIjoiYzBjMGE5MDMxNzM2NGU3Mjg1NDAxYmVjODE1NDI4ODciLCJwIjoiaiJ9 )
Re: CAS validation flows don't run consent checking interceptor ( https://shibboleth.atlassian.net/browse/IDP-1919?atlOrigin=eyJpIjoiYzBjMGE5MDMxNzM2NGU3Mjg1NDAxYmVjODE1NDI4ODciLCJwIjoiaiJ9 )
I worked around this by forcing the user to set _shib_idp_rememberConsent in this situation. My current attribute-release.vm is attached if your are interested. It also contains the same logic when the SAML-SP is allowed to do attribute query.
What I tried but did not get working is showing a different message if the OIDC-RP requests offline_access scope. That would require calling DefaultRequestedScopeLookupFunction.doLookup() but I did not find a way of getting a hold of the required AuthenticationRequest in the template.
attribute-release.vm ( https://shibboleth.atlassian.net/secure/attachment/10645/10645_attribute-release.vm )
( https://shibboleth.atlassian.net/browse/IDP-1919#add-comment?atlOrigin=eyJpIjoiYzBjMGE5MDMxNzM2NGU3Mjg1NDAxYmVjODE1NDI4ODciLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1919#add-comment?atlOrigin=eyJpIjoiYzBjMGE5MDMxNzM2NGU3Mjg1NDAxYmVjODE1NDI4ODciLCJwIjoiaiJ9 )
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:8522567 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/10920bcb/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-b36ae2b3-c43e-49e0-b075-54350c6a155d
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/10920bcb/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-6bea45bb-07da-4dee-8834-7fb37c662bf2
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/10920bcb/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-link_attachment_7-7427c63e-7d43-487a-b1dd-6a1831fa8410
Type: image/gif
Size: 163 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/10920bcb/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-01b00c39-a3bd-49ab-b3b3-9bcfd5af84ee
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220315/10920bcb/attachment-0005.png>
More information about the commits
mailing list