Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

[FEATURE] Make SSL authorization work in Pulsar's way #56

Open
jiazhai opened this issue Dec 27, 2019 · 0 comments
Open

[FEATURE] Make SSL authorization work in Pulsar's way #56

jiazhai opened this issue Dec 27, 2019 · 0 comments
Labels

Comments

@jiazhai
Copy link
Contributor

jiazhai commented Dec 27, 2019

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.

@jiazhai jiazhai added the type/feature Indicates new functionality label Dec 27, 2019
@jiazhai jiazhai changed the title [FEATURE] In SSL auth, need to map CN to pulsar role [FEATURE] Make SSL authorization work in Pulsar's way Dec 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants