This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 137
[FEATURE] Separate authorization from authentication #236
Labels
Comments
Demogorgon314
added a commit
that referenced
this issue
Aug 17, 2021
BewareMyPower
pushed a commit
that referenced
this issue
Aug 19, 2021
Demogorgon314
added a commit
that referenced
this issue
Aug 21, 2021
Add authorization to handleTopicMetadataRequest(#236 ). Fix #415 and #571 ## Motivation When client fetch metadata need check topic permission, so we need add authorization in handleTopicMetadataRequest, and do not perform role verification in authentication. ## Modifications Add a common method in `KafkaRequestHandler#authorize` , this method use `authorizer` to authorization. Modify the authentication behavior, and do not verify the role during authentication, verify the role in fetch metadata(#571 )
wangjialing218
pushed a commit
to wangjialing218/kop
that referenced
this issue
Aug 24, 2021
…ative#662) Add authorization to handleTopicMetadataRequest(streamnative#236 ). Fix streamnative#415 and streamnative#571 ## Motivation When client fetch metadata need check topic permission, so we need add authorization in handleTopicMetadataRequest, and do not perform role verification in authentication. ## Modifications Add a common method in `KafkaRequestHandler#authorize` , this method use `authorizer` to authorization. Modify the authentication behavior, and do not verify the role during authentication, verify the role in fetch metadata(streamnative#571 )
BewareMyPower
pushed a commit
that referenced
this issue
Aug 25, 2021
Add authorization to handleTopicMetadataRequest(#236 ). Fix #415 and #571 ## Motivation When client fetch metadata need check topic permission, so we need add authorization in handleTopicMetadataRequest, and do not perform role verification in authentication. ## Modifications Add a common method in `KafkaRequestHandler#authorize` , this method use `authorizer` to authorization. Modify the authentication behavior, and do not verify the role during authentication, verify the role in fetch metadata(#571 )
BewareMyPower
pushed a commit
that referenced
this issue
Aug 26, 2021
## Motivation #236 Add authorization to produce and consumer ## Modifications * Add authorization to `handleProduceRequest` * Add authorization to `handleOffsetFetchRequest` * Add authorization to `handleListOffsetRequest` * Add authorization to `MessageFetchContext#handleFetch` * Add new test units for produce or consume permissions * Add new test units for topic level permissions
BewareMyPower
pushed a commit
that referenced
this issue
Aug 26, 2021
## Motivation #236 Add authorization to produce and consumer ## Modifications * Add authorization to `handleProduceRequest` * Add authorization to `handleOffsetFetchRequest` * Add authorization to `handleListOffsetRequest` * Add authorization to `MessageFetchContext#handleFetch` * Add new test units for produce or consume permissions * Add new test units for topic level permissions
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
KoP checks permissions only during authentication. Some tests of
SaslPlainTest
relies on the behavior. But it means once a client passed the authentication, it would have all permissions no matter what the specific permissions real it have.Describe the solution you'd like
Create an
Authorizer
inKafkaRequestHandler
which is constructed from info of authentication. Then do the authorization before each request is processed.Task list
The text was updated successfully, but these errors were encountered: