cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-6928) Custom Authenticator using LDAP
Date Tue, 25 Mar 2014 22:03:15 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-6928.
------------------------------------------

    Resolution: Won't Fix

It doesn't defeat the purpose of custom authentication, it still lets you define how the actual
authentication is supposed to happen. Requiring a CREATE USER for every user, even with a
custom authenticator, was an intentional design decision, and is also how RDBMSs like PostrgreSQL
and Oracle do things.

> Custom Authenticator using LDAP
> -------------------------------
>
>                 Key: CASSANDRA-6928
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6928
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Windows
>            Reporter: Kathiresan Selvaraj
>            Priority: Minor
>
> While using LDAP server for authentication by implemting Cassandra's IAuthenticator,
authenticate() is invoked. After this, login() method of org.apache.cassandra.service.ClientState
is invoked from  login method in CassandraServer.java. This checks for the user names presence
in 'system_auth.users' table which defeats the purpose of custom authentication. Now i need
to add users to the system_auth.users table as well to complete the authentication. Please
advice.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message