Re: Internal Security - Authentication & Authorization

2017-03-15 Thread Sam Tunnicliffe
> > Here is what I have pieced together. Please let me know if I am on the > right track. You're more or less right regarding the built in authenticator/authorizer/role manager (which are usually referred to as "internal" as they store their data in Cassandra tables). One important thing to note

Re: Internal Security - Authentication & Authorization

2017-03-15 Thread kurt greaves
Jacob, seems you are on the right track however my understanding is that only the user that was auth'd has their permissions/roles/creds cached. Also. Cassandra will query at QUORUM for the "cassandra" user, and at LOCAL_ONE for *all* other users. This is the same for creating users/roles.

Re: Internal Security - Authentication & Authorization

2017-03-14 Thread Jai Bheemsen Rao Dhanwada
I have similar question. when we create users or roles what is the consistency level used? I know, If NOT EXISTS will use SERIAL consistency. what consistency will be used if just use CREATE USER ? On Mon, Mar 13, 2017 at 7:09 PM, Jacob Shadix wrote: > I'm looking for a