Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: error (athena.apache.org: local policy)
Message-ID: <51BF8DDF.6020604@mebigfatguy.com>
Date: Mon, 17 Jun 2013 18:29:51 -0400
From: Dave Brosius <dbrosius@mebigfatguy.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Custom 1.2 Authentication plugin will not work unless user is
 in system_auth.users column family
References: <1371503553.41477.YahooMailNeo@web142802.mail.bf1.yahoo.com>
In-Reply-To: <1371503553.41477.YahooMailNeo@web142802.mail.bf1.yahoo.com>
Content-Type: multipart/alternative;
 boundary="------------040201030604020604050901"

This is a multi-part message in MIME format.
--------------040201030604020604050901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

It seems to me that isExistingUser should be pushed down to the 
IAuthenticator implementation.

Perhaps you should add a ticket to 
https://issues.apache.org/jira/browse/CASSANDRA

On 06/17/2013 05:12 PM, Bao Le wrote:
> Hi,
>
>   We have a custom  authenticator that works well with Cassandra 1.1.5.
> When upgrading to C* 1.2.5, authentication failed. Turn out that in 
> ClientState.login, we make a call to Auth.isExistingUser(user.getName())
> if the AuthenticatedUser is not Anonymous user. This isExistingUser 
> method does a query on system_auth.users and if it cannot find the 
> name there, throw an exception.
>
>   If our authentication model involves exchanging data on the fly and 
> not relying on pre-created users, how do we bypass this check? Should we
> add a method on IAuthenticator to specify whether user look-up is 
> needed or not?
>
> Bao
>
>
>


--------------040201030604020604050901
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">It seems to me that isExistingUser
      should be pushed down to the IAuthenticator implementation.<br>
      <br>
      Perhaps you should add a ticket to
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <a href="https://issues.apache.org/jira/browse/CASSANDRA">https://issues.apache.org/jira/browse/CASSANDRA</a><br>
      <br>
      On 06/17/2013 05:12 PM, Bao Le wrote:<br>
    </div>
    <blockquote
      cite="mid:1371503553.41477.YahooMailNeo@web142802.mail.bf1.yahoo.com"
      type="cite">
      <div style="color:#000; background-color:#fff; font-family:times
        new roman, new york, times, serif;font-size:12pt">Hi,<br>
        &nbsp;<br>
        &nbsp; We have a custom&nbsp; authenticator that works well with Cassandra
        1.1.5.<br>
        When upgrading to C* 1.2.5, authentication failed. Turn out that
        in ClientState.login, we make a call to
        Auth.isExistingUser(user.getName())<br>
        if the AuthenticatedUser is not Anonymous user. This
        isExistingUser method does a query on system_auth.users and if
        it cannot find the name there, throw an exception.<br>
        <br>
        &nbsp; If our authentication model involves exchanging data on the
        fly and not relying on pre-created users, how do we bypass this
        check? Should we <br>
        add a method on IAuthenticator to specify whether user look-up
        is needed or not?<br>
        <br>
        Bao <br>
        <br>
        <br>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040201030604020604050901--