Skip to content
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

[FEATURE] Make Authorization and Token endpoints configurable #595

Open
mkazia-db opened this issue Mar 26, 2024 · 1 comment
Open

[FEATURE] Make Authorization and Token endpoints configurable #595

mkazia-db opened this issue Mar 26, 2024 · 1 comment

Comments

@mkazia-db
Copy link

Problem Statement
The SDK currently has fixed logic to "discover" the OAuth endpoints based on host or account_id specified in the config. This limits the flexibility for the user to specify which OAuth service they want to use for the authentication.

Proposed Solution
The SDK Config class should have an optional parameter for specifying oidc_endpoints. If this parameter is not specified, the current logic for discovering the endpoints should be used. If this is specified these endpoints should be used for U2M and M2M flows instead of discovering the endpoints.

Additional Context
There are few customers that have custom OAuth configuration. Even other customers who are on Azure and GCP may want to have flexibility to use the Azure/GCP OAuth providers or the Databricks native OAuth providers.

@benc-db
Copy link

benc-db commented Apr 10, 2024

And OAuth redirect url, and don't ignore user-supplied scopes in OAuthClient just because the workspace is in Azure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants