Loahrs commented on issue #433: URL: https://github.com/apache/pulsar-helm-chart/issues/433#issuecomment-1895634391
When I use the "proxy-admin" superuser token created as a secret when setting up the cluster (taken from the secret: "pulsar-token-proxy-admin" I still get the error. From the logs I can see that it authenticates as proxy-admin: ``` 2024-01-17T11:30:49,718+0000 [pulsar-proxy-io-2-3] INFO org.apache.pulsar.proxy.server.ProxyConnection - [/10.224.1.47:5649] complete connection, init proxy handler. authenticated with token role proxy-admin, hasProxyToBrokerUrl: false ``` I connected to one of my brokers and ran `grep Roles /pulsar/conf/broker.conf`: ``` #role as proxyRoles - it will demand to see a valid original principal. proxyRoles=proxy-admin superUserRoles=admin,broker-admin,proxy-admin ``` My proxy still logs: ``` 2024-01-17T11:30:49,762+0000 [pulsar-proxy-io-2-2] WARN org.apache.pulsar.client.impl.ClientCnx - [id: 0x1e3fd8a8, L:/10.224.1.6:35394 - R:pulsar-broker.pulsar.svc.cluster.local/10.224.1.54:6651] Received error from server: Invalid roles. ``` Could the proxy-admin Token be misconfigured somehow? How could I check that? Also I could try completely deleting everything in my cluster and installing again from scratch instead of using helm upgrades. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
