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

Jeremiah Jordan updated CASSANDRA-10873:
----------------------------------------
    Description: 
When sstableloader was changed to use native protocol instead of thrift there 
was a regression in that now sstableloader (BulkLoader) only takes {{username}} 
and {{password}} as credentials so only works with the 
{{PlainTextAuthProvider}} provided by the java driver.

Previously it allowed 3rd party auth providers to be used, we need to add back 
that ability by allowing the full classname of the auth provider to be passed 
as a parameter.

  was:
sstableloader (BulkLoader) currently only takes {{username}} and {{password}} 
as credentials so only works with the {{PlainTextAuthProvider}} provided by the 
java driver.

It should allow 3rd party auth providers to be used by allowing the full 
classname of the auth provider to be passed as a parameter.


> Allow sstableloader to work with 3rd party authentication providers
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-10873
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10873
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Mike Adamson
>            Assignee: Mike Adamson
>             Fix For: 3.0.x
>
>
> When sstableloader was changed to use native protocol instead of thrift there 
> was a regression in that now sstableloader (BulkLoader) only takes 
> {{username}} and {{password}} as credentials so only works with the 
> {{PlainTextAuthProvider}} provided by the java driver.
> Previously it allowed 3rd party auth providers to be used, we need to add 
> back that ability by allowing the full classname of the auth provider to be 
> passed as a parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to