Skip to content

Commit

Permalink
Issue 4456: add sasl-client jar into server distribution (apache#4457)
Browse files Browse the repository at this point in the history
Fixes apache#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`
  • Loading branch information
jiazhai authored and sijie committed Jun 4, 2019
1 parent ec8961f commit db3a056
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 1 deletion.
6 changes: 6 additions & 0 deletions distribution/server/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,12 @@
<version>${project.version}</version>
</dependency>

<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>
Expand Down
12 changes: 11 additions & 1 deletion site2/docs/security-kerberos.md
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down

0 comments on commit db3a056

Please sign in to comment.