You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alexey Zotov (Jira)" <ji...@apache.org> on 2021/04/04 21:05:00 UTC
[jira] [Comment Edited] (CASSANDRA-16404) Provide a nodetool way of
invalidating auth caches
[ https://issues.apache.org/jira/browse/CASSANDRA-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314070#comment-17314070 ]
Alexey Zotov edited comment on CASSANDRA-16404 at 4/4/21, 9:04 PM:
-------------------------------------------------------------------
[~blerer]
Thanks for the details, they helped a lot! I raised a draft PR ([https://github.com/apache/cassandra/pull/950]) to validate the direction I follow, your feedback would be very helpful. Also, I posted a few questions related to the implementation.
Once you confirm the direction, I'm going to make a round of local testing to ensure the functionality works as expected.
was (Author: azotcsit):
[~blerer]
Thanks for the details, they helped a lot! I raised a draft PR to validate the direction I follow, your feedback would be very helpful. Also, I posted a few questions related to the implementation.
Once you confirm the direction, I'm going to make a round of local testing to ensure the functionality works as expected.
> Provide a nodetool way of invalidating auth caches
> --------------------------------------------------
>
> Key: CASSANDRA-16404
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16404
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
> Reporter: Sumanth Pasupuleti
> Assignee: Sumanth Pasupuleti
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We currently have nodetool commands to invalidate certain caches like KeyCache, RowCache and CounterCache.
> Being able to invalidate auth caches as well can come in handy in situations where, critical backend auth changes may need to be in effect right away for all the connections, especially in configurations where cache validity is chosen to be for a longer duration. An example can be that an authenticated user "User1" is no longer authorized to access a table resource "table1" and it is vital that this change is reflected right away, without having to wait for cache expiry/refresh to trigger.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org