You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by si...@apache.org on 2019/06/04 18:42:47 UTC
[pulsar] branch master updated: Issue 4456: add sasl-client jar
into server distribution (#4457)
This is an automated email from the ASF dual-hosted git repository.
sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new db3a056 Issue 4456: add sasl-client jar into server distribution (#4457)
db3a056 is described below
commit db3a056abbf3e841e4dee79067db516a5bc64195
Author: Jia Zhai <zh...@apache.org>
AuthorDate: Wed Jun 5 02:42:41 2019 +0800
Issue 4456: add sasl-client jar into server distribution (#4457)
Fixes #4456
### Motivation
sometimes, user may use sasl client directly, e.g. use cli command bin/pulsar-client, and if sasl-client not included in, it may meet error of `class not found`
---
distribution/server/pom.xml | 6 ++++++
site2/docs/security-kerberos.md | 12 +++++++++++-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/distribution/server/pom.xml b/distribution/server/pom.xml
index f626df0..42b7300 100644
--- a/distribution/server/pom.xml
+++ b/distribution/server/pom.xml
@@ -60,6 +60,12 @@
<dependency>
<groupId>org.apache.pulsar</groupId>
+ <artifactId>pulsar-client-auth-sasl</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+
+ <dependency>
+ <groupId>org.apache.pulsar</groupId>
<artifactId>pulsar-client-tools</artifactId>
<version>${project.version}</version>
<exclusions>
diff --git a/site2/docs/security-kerberos.md b/site2/docs/security-kerberos.md
index 9f431d0..de69193 100644
--- a/site2/docs/security-kerberos.md
+++ b/site2/docs/security-kerberos.md
@@ -127,7 +127,17 @@ Make sure that the keytabs configured in the `pulsar_jaas.conf` file and kdc ser
### Kerberos configuration for clients
-In client, we need to configure the authentication type to use `AuthenticationSasl`, and also provide the authentication parameters to it.
+In client application, include `pulsar-client-auth-sasl` in your project dependency.
+
+```
+ <dependency>
+ <groupId>org.apache.pulsar</groupId>
+ <artifactId>pulsar-client-auth-sasl</artifactId>
+ <version>${pulsar.version}</version>
+ </dependency>
+```
+
+configure the authentication type to use `AuthenticationSasl`, and also provide the authentication parameters to it.
There are 2 parameters needed:
- `saslJaasClientSectionName` is corresponding to the section in JAAS configuration file for client;