thinkORo opened a new issue, #835: URL: https://github.com/apache/arrow-ballista/issues/835
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** I'd like to restrict the access to the data via a x-based-access-control pattern (x could be a Role or an Attribute). For that we need two different things: 1. authentication 2. authorization **Describe the solution you'd like** for 1.: at least a username and password must be defined (for instance via a user.list file) or, in the second step, a specific IAM provider like keycloak for 2.: a way to grant or revoke permissions on different objects This feature could be implemented step by step with a simple authentication which would increase the current (non-exsisting?) security solution in Arrow Ballista. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
