[CASSANDRA-16404] Provide a nodetool way of invalidating auth caches

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1-alpha1, 4.1
• Component/s: Feature/Authorization
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/f9aa19e3b116c0078019e9382d1a6c4bb050f113

Test and Documentation Plan

The changes are covered by unit tests. After the patch is reviewed, I'll make one round of manual testing. As far as I understand, nodetool documentation is being generated automatically, so no separate steps with regard to documentation.

• Assignee: Aleksei Zotov
• Reporter: Sumanth Pasupuleti

Authors

Aleksei Zotov

Reviewers

Benjamin Lerer, Sam Tunnicliffe, Sumanth Pasupuleti

• Created: 25/Jan/21 08:18
• Updated: 27/May/22 19:25
• Resolved: 03/Sep/21 07:35

Description

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.

Issue Links

• is related to: CASSANDRA-16914 Implement Virtual Tables for Auth Caches