You are running into https://issues.apache.org/jira/browse/CASSANDRA-7967 .
This is fixed in 2.0.11 and 2.1.1, until then I believe you will need to
explicitly grant select permission onto system.schema_triggers to the user
as a workaround.
On Sun, Sep 28, 2014 at 12:53 PM, Jens Rantil <jens.ran...@tink.se> wrote:
> Hi Pinak,
>
> Just making sure, have you set authenticator and authoriser in
> cassandra.yml?
>
> Cheers,
> Jens
>
> ——— Jens Rantil Backend engineer Tink AB Email: jens.ran...@tink.se
> Phone: +46 708 84 18 32 Web: www.tink.se Facebook Linkedin Twitter
>
>
> On Sun, Sep 28, 2014 at 11:08 AM, Pinak Pani <
> nishant.has.a.quest...@gmail.com> wrote:
>
>> Hi,
>>
>> I have been toying around with CQL. I realized when I GRANT SELECT I lose
>> authentication. Here is the process: Can someone point out what is wrong?
>>
>> ➜ apache-cassandra-2.1.0 bin/cqlsh -u cassandra -p cassandra
>>
>> Connected to Test Cluster at 127.0.0.1:9042.
>> [cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
>> Use HELP for help.
>>
>> cqlsh> CREATE USER testuser WITH PASSWORD 'abc';
>> cqlsh> GRANT SELECT ON demo_cql.grant_test TO testuser;
>> cqlsh> exit
>> ➜ apache-cassandra-2.1.0 bin/cqlsh -u testuser -p abc -k demo_cql -e
>> 'select * from grant_test'
>> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
>> Unauthorized(u'code=2100 [Unauthorized] message="User testuser has no
>> SELECT permission on <table system.schema_triggers> or any of its
>> parents"',)})
>>
>> Thanks,
>> Pinak
>>
>
>
