Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] - Authentication and Authorization Mechanisms #65

Open
aeldin opened this issue Mar 7, 2024 · 0 comments
Open

[FEATURE] - Authentication and Authorization Mechanisms #65

aeldin opened this issue Mar 7, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@aeldin
Copy link
Contributor

aeldin commented Mar 7, 2024

Add a mechanism for authenticating and authorizing clients, including username/password authentication and access control based on client roles.

  1. Username/Password Authentication:
    Implement a mechanism to require clients to provide a valid username and password during the connection handshake. This ensures that only authenticated clients can connect to the server. The credentials can be stored securely on the server side, and the client must provide the correct combination to establish a connection.

  2. Access Control Based on Client Roles:
    Introduce the concept of roles for clients, allowing you to define specific permissions or access levels for different clients. For example, you might have clients with roles like "admin," "publisher," or "subscriber." Based on the role, you can enforce restrictions on actions such as publishing or subscribing to specific topics.

@aeldin aeldin added the enhancement New feature or request label Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant