[
https://issues.apache.org/jira/browse/CASSANDRA-19984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago L. Alves updated CASSANDRA-19984:
---------------------------------------
Test and Documentation Plan: Ensure CI is green
Status: Patch Available (was: Open)
https://github.com/apache/cassandra/pull/3602
> Allow Custom Authenticators to follow negotiation logic already implemented
> in Drivers
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19984
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19984
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
> Reporter: Tiago L. Alves
> Assignee: Tiago L. Alves
> Priority: Normal
>
> Upon a client connection to the C*, the server sends a startup message with
> the full qualified class name (FQCN) of the authenticator that is used. The
> different drivers recognize this FQCN to enable scheme negotiation allowing
> different authentication methods. See for instance
> https://github.com/apache/cassandra-java-driver/blob/4.x/core/src/main/java/com/datastax/dse/driver/api/core/auth/BaseDseAuthenticator.java#L76
> Using a custom authenticator becomes restricted to either follow the default
> C* implementation (which doesn't allow scheme negotiation) or use the exact
> same FQCN that is already known in the drivers. The later might be
> impractical due to the restriction of having multiple implementations with
> the same FQCN.
> A possible workaround to the above problem is to allow IAuthenticator
> implementations to optionally return the Authenticator they want to emulate
> hence enabling custom IAuthenticator to use the functionality already
> implemented in the drivers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
