-
Notifications
You must be signed in to change notification settings - Fork 136
[Help Request] Role cannot be empty when authentication with the PLAIN mechanism #1929
Comments
I see you set up a Pulsar proxy, KoP might not work well with the proxy.
|
I just rechecked again, it's expected that the token you used did not work. The "sub" field is the role, which is empty. I generated a token following the guide here and you can see the "sub" field is "test_user" I think the issue is at the Pulsar side. It seems that Pulsar can work with an empty role when |
Nice catch! Fast and accurate! I did overlook this point, did not carefully compare the guide and the "sub" field in the token I generated myself, and I think I can use the token in the native pulsar client because I configured I think I should raise an issue about the "sub" field in the token to pulsar, because they don't seem to describe what rules need to be followed when generating token by self A great help, thanks! |
Problem
When authentication with the PLAIN mechanism, got the error msg: Role cannot be empty
To Reproduce
The producer code:
Screenshots
Configurations
I'm using a standalone broker. (
streamnative/sn-pulsar:2.10.2.4
)There are all the configurations under the
conf
folder:standalone.conf
client.conf
proxy.conf
broker.conf(if needed)
PS
The code I can produce messages:
The text was updated successfully, but these errors were encountered: