dimas-b commented on issue #1929: URL: https://github.com/apache/polaris/issues/1929#issuecomment-3028612819
This feels like a discussion of how the Authorization side of Polaris works (handling Principals managed by Polaris). The Client ID here basically refers to the Client Credentials flow (OAuth2). RFC [6749](https://www.rfc-editor.org/rfc/rfc6749#page-15) states that "The authorization server issues the registered client a client identifier". So, I'd say Polaris is within its role as an Authorization server in this case. That said, @fivetran-arunsuri : could you give us a bit more details why you'd like to control client IDs? Note that it is currently possible to set custom client IDs for the "root" user during boostrapping (see the `bootstrap` command from the admin tool). -- 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]
