[JIRA] (IDP-1919) CAS validation flows don't run consent checking interceptor

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Mon Mar 14 19:03:00 UTC 2022


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

Re: CAS validation flows don't run consent checking interceptor ( https://shibboleth.atlassian.net/browse/IDP-1919?atlOrigin=eyJpIjoiNjFkZjQxYjY1MGY1NDY0OTliODNiMDRhZTc1NjY5NzkiLCJwIjoiaiJ9 )

No, you can’t downgrade safely. I mean, it might work, but I wouldn’t expect it to. I just take snapshots of the critical folders (conf, views, etc.)

You can’t actually just define a flow like that, you’d have to duplicate the flow definition files. You don’t need to do that. Just recreate profile-intercept.xml if need be and define the old bean list of available flows and put in a copy of the flow descriptor bean with the “bad” activation condition, with the corrected condition you want to use instead. Basically copy the file from 4.0, strip out all the other descriptors, and edit the attribute-release one.

( https://shibboleth.atlassian.net/browse/IDP-1919#add-comment?atlOrigin=eyJpIjoiNjFkZjQxYjY1MGY1NDY0OTliODNiMDRhZTc1NjY5NzkiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1919#add-comment?atlOrigin=eyJpIjoiNjFkZjQxYjY1MGY1NDY0OTliODNiMDRhZTc1NjY5NzkiLCJwIjoiaiJ9 )

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:81e20ed )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220314/c7e8c067/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-66e18285-5a0f-4a49-bb77-164c8b6ec411
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220314/c7e8c067/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-4f87fad1-4695-4382-adb8-81479f9df007
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220314/c7e8c067/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-28cbcd21-0226-41fb-bc3f-f8d04b0cc2a1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220314/c7e8c067/attachment-0005.png>


More information about the commits mailing list