You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
This is related to SSL authentication that implemented in #45, After 45, user could enable authentication using SSL. But the authorization is not align with Pulsar. Most user would like to have both authentication and authorization worked.
In SSL auth, try to map CN to pulsar role, and leverage current pulsar authorise to do the authorization. then we could get pulsar-admin and pulsar io path authorised.
Currently, in KoP, all the auth with Pulsar side is through Pulsar admin client and Pulsar client (Both get from PulsarService directly). This way we could isolate KoP auth and Pulsar auth. So this task is not in a hurry.
The text was updated successfully, but these errors were encountered:
This is related to SSL authentication that implemented in #45, After 45, user could enable authentication using SSL. But the authorization is not align with Pulsar. Most user would like to have both authentication and authorization worked.
In SSL auth, try to map CN to pulsar role, and leverage current pulsar authorise to do the authorization. then we could get pulsar-admin and pulsar io path authorised.
Currently, in KoP, all the auth with Pulsar side is through Pulsar admin client and Pulsar client (Both get from PulsarService directly). This way we could isolate KoP auth and Pulsar auth. So this task is not in a hurry.
The text was updated successfully, but these errors were encountered: