<@U078Y59KC3B> how can I have a user for Pulsar Ma...
# ask-ai
s
@RunLLM how can I have a user for Pulsar Manager such that the user only has read access?
r
To create a user for Pulsar Manager with read-only access, assign the "read-only" role to the user. This role allows users to view clusters, tenants, namespaces, users, functions, and connectors, but does not permit any modifications or deletions. You can assign this role via the StreamNative Console when inviting or editing a user, or by modifying their roles if they are already part of your organization. Only Organization Admins can modify user roles in the console. For more details on role capabilities and assignment, see StreamNative Cloud RBAC documentation. Would you like step-by-step instructions for this process? Sources: - StreamNative Cloud RBAC documentation ๐Ÿ‘ 0 button ๐Ÿ‘Ž 0 button ๐Ÿ’ก Hint: Mention @runllm in the thread for followups.
s
@RunLLM I want to run Pulsar Cluster and Pulsar Manager without using StreamNative. So can I have a user for Pulsar Manager such that the user only has read access?
r
Yes, you can create a read-only user for Pulsar Manager in a self-managed Pulsar deployment, but Pulsar Manager itself does not provide built-in user/role management or fine-grained RBAC. Instead, access control is enforced by Pulsarโ€™s own authentication and authorization system. To achieve read-only access, create a Pulsar role (user) and grant it only "describe" (read) permissions on the relevant tenants, namespaces, and topics using Pulsarโ€™s admin tools. You must configure Pulsar Manager to authenticate as this user, and ensure the user is only granted permissions like
namespaces:describe
,
topics:describe
, etc. For more, see Pulsar permissions management. Would you like a step-by-step example of the required commands? Sources: - Pulsar permissions management ๐Ÿ‘ 0 button ๐Ÿ‘Ž 0 button ๐Ÿ’ก Hint: Mention @runllm in the thread for followups.
s
@RunLLM how can I create a user for Pulsar? Can Pulsar users be used to access Pulsar Manager UI?
r
Pulsar does not have a built-in user database; instead, "users" are represented by authentication credentials (such as JWT tokens, certificates, or OAuth2 identities). You create a "user" by generating credentials and assigning a role (a string identifier) to those credentials. These roles are then granted permissions in Pulsar. Pulsar Manager can use these same credentials for authentication if configured accordingly (e.g., with JWT or OAuth2). So, yes, Pulsar users (roles with valid credentials) can be used to access the Pulsar Manager UI if Pulsar Manager is set up to use the same authentication method. For more, see Pulsar security overview and Pulsar Manager authentication. Would you like details on generating credentials or configuring Pulsar Manager? Sources: - Pulsar security overview - Pulsar Manager authentication ๐Ÿ‘ 0 button ๐Ÿ‘Ž 0 button ๐Ÿ’ก Hint: Mention @runllm in the thread for followups.
s
@RunLLM can you give me details on generating credentials?
r
To generate credentials for a Pulsar user, you typically use JWT tokens. First, create a secret key (for symmetric) or a key pair (for asymmetric). Then, generate a token with a subject (role) that represents your user. For example: 1. Create a secret key:
Copy code
bin/pulsar tokens create-secret-key --output my-secret.key
2. Generate a token for a user (role):
Copy code
bin/pulsar tokens create --secret-key file:///path/to/my-secret.key --subject my-user
This prints a JWT token string, which you use as the credential for the user. You can then grant permissions to this role in Pulsar. For more, see Pulsar JWT authentication. Would you like details on assigning permissions or using the token in clients? Sources: - Pulsar JWT authentication ๐Ÿ‘ 0 button ๐Ÿ‘Ž 0 button ๐Ÿ’ก Hint: Mention @runllm in the thread for followups.