2019-10-08 10:17:06 UTC - jia zhai: Is this related with config of : ``` brokerClientAuthenticationPlugin= brokerClientAuthenticationParameters= ``` ---- 2019-10-08 10:17:36 UTC - jia zhai: <https://github.com/apache/pulsar/issues/4560#issuecomment-513113595> ---- 2019-10-08 10:35:23 UTC - tuteng: Please set authenticationProviders parameter according to this document. <https://pulsar.apache.org/docs/en/security-token-admin/#on-brokers> @Kendall Magesh-Davis ---- 2019-10-08 11:54:49 UTC - Kendall Magesh-Davis: so I use *that* JWT, specifically? `brokerClientAuthenticationParameters=token:eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ0ZXN0LXVzZXIifQ.9OHgE9ZUDeBTZs7nSMEFIuGNEX18FLR3qvy8mqxSxXw`
I had assumed I should replace it with my own ---- 2019-10-08 12:20:42 UTC - tuteng: Please set a value for the authenticationProviders or anonymousUserRole parameter in configuration file broker.conf. ---- 2019-10-08 18:59:12 UTC - Kendall Magesh-Davis: Well, I’m getting somewhere. ```18:58:06.221 [pulsar-io-24-2] WARN org.apache.pulsar.broker.service.ServerCnx - [/10.50.0.98:47546] Unable to authenticate javax.naming.AuthenticationException: Failed to authentication token: The parsed JWT indicates it was signed with the RS512 signature algorithm, but the specified signing key of type javax.crypto.spec.SecretKeySpec may not be used to validate RS512 signatures. Because the specified signing key reflects a specific and expected algorithm, and the JWT does not reflect this algorithm, it is likely that the JWT was not expected and therefore should not be trusted. Another possibility is that the parser was configured with the incorrect signing key, but this cannot be assumed for security reasons.``` ---- 2019-10-08 23:56:55 UTC - tuteng: Please confirm that the token you generated and copied is correct. References: <https://pulsar.apache.org/docs/en/security-token-admin/> ----
