We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Rbac with keycloak provider.
Rbac with keycloak provider
No response
0.7.1
The text was updated successfully, but these errors were encountered:
Hello there AungKoKoPyae! 👋
Thank you and congratulations 🎉 for opening your very first issue in this project! 💖
In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀
Sorry, something went wrong.
I found some useful for auth with keycloak. we can authticate with keycloak and use rbac with oauth .
auth: type: OAUTH2 oauth2: client: keycloak: clientId: xxx clientSecret: yyy scope: openid issuer-uri: https://<keycloak_instance>/auth/realms/ user-name-attribute: preferred_username client-name: keycloak provider: keycloak custom-params: type: keycloak
this custom parms to change custom-params: type: oauth roles-field: roles
for rbac
rbac: roles: - name: "kafka-admin" clusters: - local-kafka subjects: - provider: oauth type: user value: "user1" - provider: oauth type: user value: "user2" permissions: - resource: topic value: ".*" actions: - VIEW - MESSAGES_READ
- resource: consumer value: ".*" actions: [ view ] - resource: schema value: ".*" actions: [ view ] - resource: connect value: ".*" actions: [ view ] - resource: acl value: ".*" actions: [ view ]
This can work only for specific user not for group with kafka. but this is useful before group rbac with keycloak.
No branches or pull requests
Issue submitter TODO list
Is your proposal related to a problem?
Rbac with keycloak provider.
Describe the feature you're interested in
Rbac with keycloak provider
Describe alternatives you've considered
No response
Version you're running
0.7.1
Additional context
No response
The text was updated successfully, but these errors were encountered: