You can write a patch for one, or create a custom authenticator implementation
that would enforce this.
They are pluggable after all, just like authorizer is.
--
AY
On 23 December 2016 at 20:06:19, Prakash Chauhan (prakash.chau...@ericsson.com)
wrote:
Hello All,
In Apache Cassandra ,
I’d like to take issue with this sentiment. Whilst I can see the point, it is
exactly this sort of attitude that leads to sites getting hacked. You’re
argument goes, if a site using Cassandra loses 1million passwords it’s that
sites admin that is to blame. However, infosec aware developers
Hi,
actually Cassandra is not public service like e-mail or social network. It's
admin responsibility to create strong super password, and if there is front-end
application allowing to users setting password such application can force
password requirements.
Best regards, Vladimir
Hello All,
In Apache Cassandra , there are no strict password policies for creating a new
user.
A new user can be created with a password as simple as "abc" which is not at
all recommended for production use.
Moreover the same password can be used again and again.
There should be a
Added you as a contributor and assigned.
--
Michael
On 12/23/2016 09:55 AM, Prakash Chauhan wrote:
> Hi All,
>
> I have recently created a JIRA ticket
> https://issues.apache.org/jira/browse/CASSANDRA-12968 . Unfortunately I am
> not getting any option to assign it to myself.
> Can someone
Hi All,
I have recently created a JIRA ticket
https://issues.apache.org/jira/browse/CASSANDRA-12968 . Unfortunately I am not
getting any option to assign it to myself.
Can someone assign the ticket to me ?
Thanks...
Regards,
Prakash Chauhan.
