Using internal or LDAP authentication
Authenticate the DataStax Apache Pulsar™ Connector session using internal or LDAP authentication. When the cluster has internal or LDAP authentication enabled, configure the user name and password settings for DataStax Apache Pulsar™ Connector. This task also requires a login role for the DataStax Apache Pulsar™ Connector with access to the mapped tables.
-
Verify whether your cluster has internal or LDAP authentication enabled. Refer to the authentication options in the dse.yaml file. Authentication options for the DSE Authenticator allow you to use multiple schemes for authentication simultaneously in a DataStax Enterprise cluster.
-
Additional authenticator configuration is required in dse.yaml when the authorization option in cassandra.yaml is set to
com.datastax.bdp.cassandra.auth.DseAuthorizer. When authorization is enabled, the DataStax Apache Pulsar™ Connector login role must have a minimum ofmodifyprivileges on tables receiving data from the DataStax Apache Pulsar Connector. For details, refer to the authorization options. -
In dse.yaml, there are options to configure LDAP security when the authenticator option in cassandra.yaml is set to
com.datastax.bdp.cassandra.auth.DseAuthenticator. When not set, LDAP authentication is not used. The default in dse.yaml is that this setting is commented out (false). For details, refer to Defining an LDAP scheme. -
Internal and LDAP schemes can also be used for role management. Refer to the role management options.
-
Set the relevant auth parameters in dse.yaml for
auth.provider,auth.username(the login role name or LDAP username), andauth.password. See parameters.