[JIRA] (IDP-1981) Build Predicate based on RevocationCache

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Thu Jul 28 19:23:17 UTC 2022


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

Re: Build Predicate based on RevocationCache ( https://shibboleth.atlassian.net/browse/IDP-1981?atlOrigin=eyJpIjoiYTFiYWYxOTE3MzA1NDE0NGFlYjc4MGUyNTFjYmVlZGYiLCJwIjoiaiJ9 )

TBD polish:

* The RevocationContext I cooked up should be more generic, which I think can be done by making it a map of strings instead of a list, allowing the revocation syntax to be keyed by a format signal that avoids collisions between built-in approaches and extension work.
* With that change, arguably we could redesign things so that the checking for revocation against the records in the context is independent of the way the records are populated, which would lead to “you can use the resolver for that, or the RevocationCache approach, or…”

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

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#100203- sha1:db6c294 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220728/683608aa/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-8e1ad921-5be7-4c45-9542-62a6b46be69f
Type: image/png
Size: 452 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220728/683608aa/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-f9d856a9-20fc-45ac-bf1e-9e50bc5ad0ea
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220728/683608aa/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-cf828401-4c79-45c4-b511-71ba77f608b1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220728/683608aa/attachment-0005.png>


More information about the commits mailing list