Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <51B08853.10209@ids-mannheim.de>
Date: Thu, 06 Jun 2013 15:02:11 +0200
From: Michael Hanl <hanl@ids-mannheim.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: dev@cassandra.apache.org
References: <taendx2nilwchtva67653tdv.1370499194564@email.android.com>
In-Reply-To: <taendx2nilwchtva67653tdv.1370499194564@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: AW: PasswordAuthenticator

Just for the record,
I worked around this issue. Since there has been no indication what so 
ever, where this went wrong (since no log was registered), I manually 
created the user in system_auth.users and system_auth.credentials. After 
switching to PasswordAuthenticator, I could successfully log into cqlsh 
and cassandra-cli.

Greetings,

Michael

On 06/06/2013 08:13 AM, Michael Hanl wrote:
> That's the thing. I don't. Whereas the column families et successfully created, the user is not. And no, I don't have any of those messages in my logs. I checked a couple of times while restarting the nodes.
>
> Greetings
> Michael Hanl
>
> Michal Michalski <michalm@opera.com> schrieb:
>
>> Don't you have a default "cassandra" user in system_auth.users?
>>
>> cqlsh> SELECT * from system_auth.users ;
>>
>>   name      | super
>> -----------+-------
>>   cassandra |  True
>>
>> It should be created on startup and you should see this in your logs:
>>
>> "PasswordAuthenticator created default user cassandra"
>>
>> However, if it fails, you should see this:
>>
>> "Skipped default superuser setup: some nodes were not ready"
>>
>> Do you have any of these messages in your log?
>>
>> M.
>>
>> W dniu 05.06.2013 17:19, Michael Hanl pisze:
>>> Hello,
>>>
>>> Based on several examples online I was trying to use the
>>> PasswordAuthenticator on our project nodes.
>>> Although setting it up with the version 1.2.5 of cassandra was not that
>>> difficult, I cannot seem to get access neither in cqlsh nor in the CLI.
>>> Having a look at the filesystem and the schema tables (nodetool) that
>>> the respective column families have been created with the startup of
>>> cassandra, but there is no default user, which of course I need to setup
>>> my own users.
>>>
>>> I tried several repairs with the nodetool already, but obviously when
>>> there are no data in the column family, repair is kind of useless.
>>>
>>> I hope someone has an idea (besides writing my own authentiction
>>> interface implementation).
>>>
>>>
>>> Kind regards,
>>>
>>> Michael Hanl