Martin Vieth
03/20/2025, 9:32 AMRunLLM
03/20/2025, 9:32 AMLOOKUP permission to the client's role for the relevant namespace or topic. This can be done using the pulsar-admin command:
./bin/pulsar-admin namespaces grant-permission namespace --role role --actions lookup
Would you like more details on how to configure these permissions?
Sources:
- https://github.com/apache/pulsar/issues/18716
- https://github.com/apache/pulsar/pull/13771 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Martin Vieth
03/20/2025, 9:36 AMRunLLM
03/20/2025, 9:36 AMproduce, consume, functions, sources, sinks, and packages.
To resolve the "Client is not authorized to Lookup" error, you should ensure that the client has either produce or consume permissions, as these are typically required for lookup operations. You can grant these permissions using the pulsar-admin command:
./bin/pulsar-admin namespaces grant-permission namespace --role role --actions produce,consume
This command grants both produce and consume permissions to the specified role for the given namespace, which should allow the client to perform lookup operations.
Would you like more details on configuring these permissions?
Sources:
- https://github.com/apache/pulsar-client-go/blob/master/pulsaradmin/pkg/utils/auth_action.go
- https://github.com/apache/pulsar/blob/master/pulsar-client-admin-api/src/main/java/org/apache/pulsar/common/policies/data/AuthAction.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.