You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2019/10/08 09:11:03 UTC

Slack digest for #dev - 2019-10-08

2019-10-07 13:04:28 UTC - Tim Howard: @Tim Howard has joined the channel
----
2019-10-07 16:47:14 UTC - Fredrick P Eisele: @Sijie Guo Yes, I will try to get some logs for the brokers.
----
2019-10-08 05:24:17 UTC - Kendall Magesh-Davis: I seem to be missing something. I’m trying to enable JWT authentication and authorization on Pulsar 2.4.1. I’ve generated a JWT and added these ENVs to the broker’s config:
```
    authenticationEnabled: "true"
    authorizationEnabled: "true"
    superUserRoles: "super1"
    authPlugin: org.apache.pulsar.client.impl.auth.AuthenticationToken
    authParams: token:redactedmyveryown.redactedcustomizedredacted.jwtredacted```

When I startup the cluster, I get this error from the brokers:

```05:20:58.603 [pulsar-io-24-1] WARN  org.apache.pulsar.broker.service.ServerCnx - [/10.50.0.83:51732] Unable to authenticate
javax.naming.AuthenticationException: No anonymous role, and no authentication provider configured```
----
2019-10-08 05:25:16 UTC - Kendall Magesh-Davis: the helm chart automatically generates `webServiceUrl` and `brokerServiceUrl` as described here <https://pulsar.apache.org/docs/en/security-token-client/>

What am I missing?
----