-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Consider supporting ranger authorization systems? #113
Comments
Hello ! Thanks for your feature request. This could be interesting ! Just a information for you: this project doesn't implement the S3 api. It isn't that kind of proxy. It has it's own API. You will need specific development to access it in order to get your data. I hope I'm clear, tell me if not. Moreover, to be authenticated, the actual code need an OpenID Connect connection (basic auth is considered has authorized directly). |
Thank you for your reply. Yesterday, I thought about it again. In fact, I only need to do S3 permission authentication. So maybe I just need to be a proxy, intercept the request, and then do permission authentication, and if the authentication passes, send the request directly to AWS. So that I don't have to implement the specific S3 api. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days |
Is your feature request related to a problem? Please describe.
Ranger is a popular solution for big data permission verification, but it does not support AWS-S3 permission verification at present.
Describe the solution you'd like
At present, I have an idea that the Proxy intercepts the S3 request, sends the request to ranger-S3-Plugin for authorization verification, and then sends the request to AWS-S3 Server after verification.
This way, if my data is stored on S3, I can use proxy to do request interception and permission authentication as well.
Reference link: https://github.com/apache/ranger
The text was updated successfully, but these errors were encountered: