Had found the same thing, and updated:
http://wiki.apache.org/cassandra/SimpleAuthenticator
On 10/27/2011 04:25 PM, RobinUs2 wrote:
It seems that org.apache.cassandra.auth.SimpleAuthenticator is missing in the
cassandra 1.0 binaries. Is this on purpose or did I found a bug?
--
View this
7;t find it in the first place.
>
> What would you suggest for authentication? Firewall rules that only allow
> from whitelist hosts? Writing a custom Authenticator?
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Simpl
46.n2.nabble.com/SimpleAuthenticator-missing-in-Cassandra-1-0-tp6937930p6937981.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
ontext:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/SimpleAuthenticator-missing-in-Cassandra-1-0-tp6937930p6937930.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
>
--
Jonathan Ellis
Project Chair, Apache Cassa
On Thu, Oct 27, 2011 at 3:25 PM, RobinUs2 wrote:
> It seems that org.apache.cassandra.auth.SimpleAuthenticator is missing in the
> cassandra 1.0 binaries. Is this on purpose or did I found a bug?
>From NEWS.txt:
- The SimpleAuthenticator and SimpleAuthority classes have been
It seems that org.apache.cassandra.auth.SimpleAuthenticator is missing in the
cassandra 1.0 binaries. Is this on purpose or did I found a bug?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/SimpleAuthenticator-missing-in-Cassandra-1-0
Thanks for the answer.
- Pierre
-Original Message-
From: Yi Yang
Date: Thu, 20 Oct 2011 04:20:25
To: ;
Subject: Re: SimpleAuthenticator / SimpleAuthorization missing
See:
https://issues.apache.org/jira/browse/CASSANDRA-2922
On Thu, Oct 20, 2011 at 4:08 AM, Pierre Chalamet wrote
See:
https://issues.apache.org/jira/browse/CASSANDRA-2922
On Thu, Oct 20, 2011 at 4:08 AM, Pierre Chalamet wrote:
> Hello,
>
> SimpleAuthenticator & SimpleAuthorization just disappear in release
> 1.0.0...
>
> Will this stay like this or is it a release bug ?
>
> Thanks,
> - Pierre
>
Hello,
SimpleAuthenticator & SimpleAuthorization just disappear in release 1.0.0...
Will this stay like this or is it a release bug ?
Thanks,
- Pierre
he apache Cassandra chair, recommends bcrypt over MD5 for a
secure has function:
http://codahale.com/how-to-safely-store-a-password/
Ted Zlatanov, the Cassandra developer who implemented the MD5
SimpleAuthenticator encryption said on the user-mailing list:
“I used MD5 when I proposed SimpleAu
See: https://issues.apache.org/jira/browse/CASSANDRA-2922
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
Thanks
On Thu, Jun 30, 2011 at 10:09 PM, aaron morton wrote:
> cassandra.in.sh is old skool 0.6 series, 0.7 series uses cassandra-env.sh.
> The packages put it in /etc/cassandra.
>
> This works for me at the end of cassandra-env.sh
>
> JVM_OPTS="$JVM_OPTS -Dpasswd.properties=/etc/cassandra/passwd
cassandra.in.sh is old skool 0.6 series, 0.7 series uses cassandra-env.sh. The
packages put it in /etc/cassandra.
This works for me at the end of cassandra-env.sh
JVM_OPTS="$JVM_OPTS -Dpasswd.properties=/etc/cassandra/passwd.properties"
JVM_OPTS="$JVM_OPTS -Daccess.properties=/etc/cassandra/ac
Hi,
I am encountering an error while trying to set up simple authentication in a
test environment.
*BACKGROUND*
*Cassandra Version: ReleaseVersion: 0.7.2-0ubuntu4~lucid1*
*OS Level: Linux cassandra1 2.6.32-32-server #62-Ubuntu SMP Wed Apr 20
22:07:43 UTC 2011 x86_64 GNU/Linux*
*2 node cluster*
P
On Wed, 18 May 2011 17:16:28 -0700 Sameer Farooqui
wrote:
SF> But even SSL/TLS is subject to attacks from tools like SSLSNIFF:
SF> http://www.thoughtcrime.org/software/sslsniff
For perfect security, unplug the server and remove the hard drive.
Ted
2:22 -0700 Sameer Farooqui <
> cassandral...@gmail.com> wrote:
> >
> > SF> Would still be nice though to use the bcrypt hash over MD5 for
> stronger
> > SF> security.
> >
> > I used MD5 when I proposed SimpleAuthenticator for two reasons:
> >
>
>
> I used MD5 when I proposed SimpleAuthenticator for two reasons:
>
> 1) SimpleAuthenticator is supposed to be a demo of the authentication
> interface. It can be used for testing and trivial setups, but I
> wouldn't use it in production. So it's meant to get you
On Tue, 17 May 2011 15:52:22 -0700 Sameer Farooqui
wrote:
SF> Would still be nice though to use the bcrypt hash over MD5 for stronger
SF> security.
I used MD5 when I proposed SimpleAuthenticator for two reasons:
1) SimpleAuthenticator is supposed to be a demo of the authentication
int
If you need it create a ticket on
https://issues.apache.org/jira/browse/CASSANDRA
Aaron
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 18 May 2011, at 10:52, Sameer Farooqui wrote:
> Opps, my bad... please ignore the email below. It
Opps, my bad... please ignore the email below. It actually works with the
plain text password (I had forgotten to update the passwd.properties file on
one node which was causing the login to fail).
Example of successful login:
ubuntu@domU-12-31-39-0C-D9-13:~/apache-cassandra-0.8.0-beta1$
bin/cassa
Hey Aaron,
Unfortunately it fails with plaintext password also:
ubuntu@domU-12-31-39-0C-D9-13:~/apache-cassandra-0.8.0-beta1$
bin/cassandra-cli -h ec2-50-19-26-189.compute-1.amazonaws.com -p 9160 -u
jdoe -pw 'nosql' -k MDR Login failure. Did you specify 'keyspace',
'username' and 'password'?
Wel
http://codahale.com/how-to-safely-store-a-password/
On Tue, May 17, 2011 at 3:03 PM, aaron morton wrote:
> Use the plain text password via the cli, the server will make a hash and
> compare it to the one in the file.
> wrt SHA-2 I'm not a security guy but MD5 is probably "good enough" for the
> p
Use the plain text password via the cli, the server will make a hash and
compare it to the one in the file.
wrt SHA-2 I'm not a security guy but MD5 is probably "good enough" for the
problem of storing passwords in plain text in a file.
Hope that helps.
-
Aaron Morton
Freela
By the way, just noticed a typo in my email below. I'm using the correct
keyspace name in all locations on the cluster... however in my examples
below, I used MyKeyspace in some spots and MDR in other spots, but in the
cluster I'm specifying the same keyspace name everywhere, so that's not the
issu
Hi all,
We are trying to use MD5 encrypted passwords. Quick question first - Is
SHA-2 supported yet? US-CERT of the U. S. Department of Homeland Security
has said that MD5 "should be considered cryptographically broken and
unsuitable for further use”, and SHA-2 family of hash functions is
recommen
Thanks, its working now...
On 11/18/2010 1:50 PM, Nick Bailey wrote:
I believe the map of credentials should be
creds.put("username", "your_username");
creds.put("password", "your_password");
So you have two entries in the map, one for user and one for password. No
idea why that call would be
I believe the map of credentials should be
creds.put("username", "your_username");
creds.put("password", "your_password");
So you have two entries in the map, one for user and one for password. No
idea why that call would be hanging though.
On Thu, Nov 18, 2010 at 1:46 PM, Alaa Zubaidi wrote:
Hi Aaron,
Thanks for the help..
If I don't use the Authenticator, and keep it at AllowAll it will work
find..
I tried provide an invalid password but it behaved the same...
Here is what i am doing:
Map creds = new HashMap();
creds.put("username", "pwd");
AuthenticationRe
I *think* that message is just from when the connection is closed.
Sorry this is a hard one to help with, as it's more than likely something to do
with your client app.
Some guessing...
Everything is working if you do not use the authenticator ?
Can you inspect the ports on the server and see
One other thing, while login() hangs when called on the server side, and
nothing is logged, I see the following logged when I kill the hanged
process.
DEBUG 13:01:10,640 logged out: null
Thanks
On 11/17/2010 12:41 PM, Alaa Zubaidi wrote:
Hi Aaron,
I used the client, and was able to login.
E
Hi Aaron,
I used the client, and was able to login.
E:\cassandra>bin\cassandra-cli.bat -host 191.111.1.11 -port 9160
Starting Cassandra Client
Connected to: "Test Cluster" on 191.111.1.11/9160
Welcome to cassandra CLI.
Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
[defa...@unknown]
Can you try using the command line cassandra-cli tool ? fire it up and look at the online help, if you pass a user name and password to the "use" statement it will perform a login after setting the keyspace for the connection. Try testing the login that way, and see what is logged server side (wit
I removed the exception handling and It seems that the login() is hanging?
On 11/15/2010 1:36 PM, Eric Evans wrote:
On Mon, 2010-11-15 at 12:26 -0800, Alaa Zubaidi wrote:
I set authority to SimpleAuthority and log4j.rootLogger=DEBUG,stdout,R
and its still the same, the error in my application
On Mon, 2010-11-15 at 12:26 -0800, Alaa Zubaidi wrote:
> I set authority to SimpleAuthority and log4j.rootLogger=DEBUG,stdout,R
>
> and its still the same, the error in my application is
> $batch_mutate_result.read(Cassandra.java:16477)
> InvalidRequestException(why: you have not logged in)
>
>
org.apache.cassandra.auth.SimpleAuthority and AllowAllAuthority...
If you are using SimpleAuthenticator then you should be using
SimpleAuthority.
I uncommitted the "Application logging options" in
log4j-server.properties, is this enough?
No, you need to set the log level on the root logger. By default that
On Mon, 2010-11-15 at 11:30 -0800, Alaa Zubaidi wrote:
> I tried both setting authority to
> org.apache.cassandra.auth.SimpleAuthority and AllowAllAuthority...
If you are using SimpleAuthenticator then you should be using
SimpleAuthority.
> I uncommitted the "Application loggi
aa Zubaidi wrote:
using SimpleAuthenticator is not working with me in beta 3
I am doing the following:
·In Cassandra.yaml Set
authenticator: org.apache.cassandra.auth.SimpleAuthenticator
·Add username and password to passwd.proprties
·Add username to keyspace and column family permission in
access
On Fri, 2010-11-12 at 17:07 -0800, Alaa Zubaidi wrote:
> using SimpleAuthenticator is not working with me in beta 3
>
> I am doing the following:
>
> ·In Cassandra.yaml Set
> authenticator: org.apache.cassandra.auth.SimpleAuthenticator
> ·Add username and password to pa
No, the sever is not logging anything
On 11/13/2010 4:27 PM, Stu Hood wrote:
Is the server logging anything during the failed authentication?
On Fri, Nov 12, 2010 at 8:07 PM, Alaa Zubaidi wrote:
using SimpleAuthenticator is not working with me in beta 3
I am doing the following
Is the server logging anything during the failed authentication?
On Fri, Nov 12, 2010 at 8:07 PM, Alaa Zubaidi wrote:
> using SimpleAuthenticator is not working with me in beta 3
>
> I am doing the following:
>
> · In Cassandra.yaml Set
using SimpleAuthenticator is not working with me in beta 3
I am doing the following:
·In Cassandra.yaml Set
authenticator: org.apache.cassandra.auth.SimpleAuthenticator
·Add username and password to passwd.proprties
·Add username to keyspace and column family permission in access.proprties
·Add
Thank you very much! It works!
2010/5/3 roger schildmeijer
> You need to define two more properties: passwd.properties and
> access.properties (hint
> -Dpasswd.properties=/user/schildmeijer/cassandra/conf/passwd.properties and
> analogous for access.properties)
>
>
>
> // Roger Schildmeijer
>
>
You need to define two more properties: passwd.properties and
access.properties (hint
-Dpasswd.properties=/user/schildmeijer/cassandra/conf/passwd.properties and
analogous for access.properties)
// Roger Schildmeijer
On Mon, May 3, 2010 at 1:06 PM, Julio Carlos Barrera Juez <
juliocar...@gmail
Hi again.
My system log says:
ERROR [pool-1-thread-1] 2010-05-03 12:54:03,801 Cassandra.java (line 1153)
Internal error processing login
java.lang.RuntimeException: Unexpected authentication problem
at
org.apache.cassandra.auth.SimpleAuthenticator.login(SimpleAuthenticator.java:113)
at
org.apache
Are you sure that your keyspace is named "keyspace", and not "Keyspace1"
(default)?
/ Roger Schildmeijer
On Thu, Apr 29, 2010 at 2:47 PM, Jonathan Ellis wrote:
> If you're getting an internalerror, you need to check the server logs
> for the exception that caused it
>
> On Wed, Apr 28, 2010
If you're getting an internalerror, you need to check the server logs
for the exception that caused it
On Wed, Apr 28, 2010 at 6:20 AM, Julio Carlos Barrera Juez
wrote:
> Hi all!
> I am using org.apache.cassandra.auth.SimpleAuthenticator to use
> authentication in my cluster with one node (with c
Hi all!
I am using org.apache.cassandra.auth.SimpleAuthenticator to use
authentication in my cluster with one node (with cassandra 0.6.1). I have
put:
org.apache.cassandra.auth.SimpleAuthenticator
in storage-conf.xml file, and:
keyspace=username
in access.properties file, and:
username=password
in
47 matches
Mail list logo
