[
https://issues.apache.org/jira/browse/CASSANDRA-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398255#comment-17398255
]
Aleksei Zotov commented on CASSANDRA-16404:
-------------------------------------------
Thanks [~samt]! I checked the build and mentioned a few failures related to the
renaming of {{NetworkAuthCache}} MBean. I fixed that and additionally
incorporated your change on the error message
([db917dfe04ffdf0cda393474dce431d749e7bded|https://github.com/apache/cassandra/pull/950/commits/db917dfe04ffdf0cda393474dce431d749e7bded]).
Also I rebased and squashed the changes into
[https://github.com/alex-ninja/cassandra/tree/cassandra-16404-trunk] branch (I
intentionally do not want to squash commits in the PR branch and keep them for
historical reference), so it is easy to kick off the CI again.
> 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: Aleksei Zotov
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 50m
> 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: [email protected]
For additional commands, e-mail: [email protected]
