[JIRA] (IDP-1886) Problem with Attribute Consent Release Page

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Fri Dec 3 16:34:40 UTC 2021


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

Re: Problem with Attribute Consent Release Page ( https://shibboleth.atlassian.net/browse/IDP-1886?atlOrigin=eyJpIjoiYWI5MTI4ZjVhNmFjNGYxZDgxZjk2YWZkMzRmZDZhMWYiLCJwIjoiaiJ9 )

The documentation isn’t really saying you’d use client storage for consent, it’s talking about why you can’t do it with cookies alone if you do.

The only practical way to deploy consent is a database (which I consider undeployable, but it’s not so bad for consent because the failure implications aren’t that severe).

But it works, we’ve tested it a lot. I haven’t done it lately but we can verify it easily enough. And it works the same way with a database, so it should fail the same way either way unless the problem is with your browser (what browser is this?)

For debugging purposes, please get a DEBUG log of the entire sequence you’re testing there. Attach that and we can at least try and spot where it should be storing the records and then failing to find them.

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

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#100183- sha1:844c6ad )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211203/20783f7d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-8aea76a7-18c4-4144-9ea6-67b9a68a49c6
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211203/20783f7d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-7017a46f-2392-4f8f-84ec-e0d3db656169
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211203/20783f7d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-0c0fc587-2cef-4684-b1af-9506752f014b
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211203/20783f7d/attachment-0005.png>


More information about the commits mailing list