You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lukasz Antoniak (Jira)" <ji...@apache.org> on 2026/07/28 15:40:00 UTC

[jira] [Created] (CASSANALYTICS-185) Support custom authentication mechanisms in Sidecar client

Lukasz Antoniak created CASSANALYTICS-185:
---------------------------------------------

             Summary: Support custom authentication mechanisms in Sidecar client
                 Key: CASSANALYTICS-185
                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-185
             Project: Apache Cassandra Analytics
          Issue Type: New Feature
            Reporter: Lukasz Antoniak
            Assignee: Lukasz Antoniak


At the moment of writing, Cassandra Analytics authenticates with Sidecar using mTLS certificate. The identity of the caller is passed in common name fields of TLS certificate. Sidecar has pluggable authentication and authorisation framework, with JWT and OAuth implementations included. Purpose of the ticket is to provide an extension point that allows Analytics users to implement their own identity providers in Sidecar client.


{code:java}
public interface SidecarIdentityProvider
{
    /**
     * Initializes identity provider.
     * @param options Spark configuration
     */
    default void initialize(Map<String, String> options, HttpClient httpClient)
    {
    }

    /**
     * Callback executed before request is build and send to Sidecar. Typical identity
     * provider will add custom HTTP headers to the request.
     * @param requestBuilder the request builder
     */
    void injectCredentials(RequestContext.Builder requestBuilder);
}
 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org