[JIRA] (IDP-2047) Get list of locked accounts

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Tue Dec 6 17:15:55 UTC 2022


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

Re: Get list of locked accounts ( https://shibboleth.atlassian.net/browse/IDP-2047?atlOrigin=eyJpIjoiNjEyNWQyOGNiOWE3NDRlNzhlMDg3NWZhY2MxZGYyYTgiLCJwIjoiaiJ9 )

It’s somewhat infeasible “by default” with the storage-based implementation because there is no API for obtaining all the keys stored in a particular context. The way around this is quite ugly and involves a lot of back-pointing index records and such that are not really scalable to maintain.

So in general there’s no way to ask what the current locked out accounts are (it would require a different implementation or querying the storage service’s back-end).

Having said that, a change could plausibly be made to store something else (maybe a list locked addresses keyed by just username), particularly if it wasn’t strictly neeeded to make the core lockout feature work (i.e., not requring cross-record transactional semantics, which aren’t possible), so could be added as a secondary addition. Will have to look into what we might be able to do.

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

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#100211- sha1:7eca2fb )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/b86e71c3/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-0533c18d-26b3-4868-beb3-2670b382ccec
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/b86e71c3/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-779831a0-648f-4609-9602-1622f77547f4
Type: image/png
Size: 448 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/b86e71c3/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-65896d97-9339-400c-ab84-9566c52e332f
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/b86e71c3/attachment-0005.png>


More information about the commits mailing list