poojanilangekar commented on PR #1925: URL: https://github.com/apache/polaris/pull/1925#issuecomment-3019871120
> relies on the Polaris administrator (service provider) to perform some per-arranged kind of auth flow This part isn't accurate. The Polaris service does not perform any pre-arranged authentication. It relies on the underlying connection library to carry out the authentication flow based on the environment or configuration file. Really what we want to convey here is that: 1. Polaris does not store or manage the authentication parameters. 2. It does not apply any authentication flow explicitly. To elaborate on 2: If the config file provides no authentication parameters, then it will use an unauthenticated mechanism, on the other hand, let's say the config file contains auth method Kerberos and provides a path to a key-tab file, then the connection library will connect to the kerberized hadoop instance. In both cases Polaris is oblivious to what happens under the hood. -- 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]
