You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "yj199522 (via GitHub)" <gi...@apache.org> on 2025/07/28 17:15:34 UTC
[D] OAuth2 client information for Big query not visible on UI [superset]
GitHub user yj199522 created a discussion: OAuth2 client information for Big query not visible on UI
I'm exploring options for connecting BigQuery to Apache Superset, specifically looking for a way to leverage OAuth2 for authentication. My goal is to enable users to establish these connections directly from the Superset UI by providing their own OAuth2 application details, such as a client ID, client secret, and authorization URL, within the database connection form itself.
Currently, I understand that:
- Superset supports OAuth2 for its own user authentication (e.g., logging into Superset via Azure OAuth), which typically involves server-side configuration in superset_config.py.
- BigQuery connections often utilize service accounts or a credentials_path pointing to a JSON key file.
- There's a Superset Improvement Proposal (SIP-85) that discusses enabling OAuth2 directly for databases like BigQuery to improve user experience by handling token storage and refresh.
My question is:
Is there a current feature, that allows end-users to dynamically configure OAuth2 for a BigQuery database connection directly within the Superset UI (e.g., through the "Connect a new database" form), where they can input the necessary OAuth2 application details (client ID, client secret, authorization URL)?
If this direct UI-based input for database connection-specific OAuth2 is not currently supported or recommended, what are the best practices or alternative approaches for managing BigQuery connections with user-level OAuth2 authentication in Superset? For instance, does the SIP-85 implementation handle this via a different user flow (e.g., an OAuth consent screen initiated from the UI after initial server-side setup)?
Any guidance, examples, or pointers to relevant documentation or discussions would be greatly appreciated!
Thank you!
GitHub link: https://github.com/apache/superset/discussions/34357
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] OAuth2 client information for Big query not visible on UI [superset]
Posted by "yj199522 (via GitHub)" <gi...@apache.org>.
GitHub user yj199522 edited a comment on the discussion: OAuth2 client information for Big query not visible on UI
I'm not able to see these option while adding new Big Query connection can you help out how can i enable this ?
<img width="530" height="526" alt="Screenshot 2025-07-28 at 1 15 59 PM" src="https://github.com/user-attachments/assets/1b521253-1088-4b12-bb0f-56de783eb2fa" />
GitHub link: https://github.com/apache/superset/discussions/34357#discussioncomment-13913017
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] OAuth2 client information for Big query not visible on UI [superset]
Posted by "yj199522 (via GitHub)" <gi...@apache.org>.
GitHub user yj199522 edited a discussion: OAuth2 client information for Big query not visible on UI
I'm exploring options for connecting BigQuery to Apache Superset, specifically looking for a way to leverage OAuth2 for authentication. My goal is to enable users to establish these connections directly from the Superset UI by providing their own OAuth2 application details, such as a client ID, client secret, and authorization URL, within the database connection form itself.
Currently, I understand that:
- Superset supports OAuth2 for its own user authentication (e.g., logging into Superset via Azure OAuth), which typically involves server-side configuration in superset_config.py.
- BigQuery connections often utilize service accounts or a credentials_path pointing to a JSON key file.
- There's a Superset Improvement Proposal (SIP-85) that discusses enabling OAuth2 directly for databases like BigQuery to improve user experience by handling token storage and refresh.
My question is:
Is there a current feature, that allows end-users to dynamically configure OAuth2 for a BigQuery database connection directly within the Superset UI (e.g., through the "Connect a new database" form), where they can input the necessary OAuth2 application details (client ID, client secret, authorization URL)?
If this direct UI-based input for database connection-specific OAuth2 is not currently supported or recommended, what are the best practices or alternative approaches for managing BigQuery connections with user-level OAuth2 authentication in Superset? For instance, does the SIP-85 implementation handle this via a different user flow (e.g., an OAuth consent screen initiated from the UI after initial server-side setup)?
Any guidance, examples, or pointers to relevant documentation or discussions would be greatly appreciated!
Thank you!
PR Reference - https://github.com/apache/superset/pull/30674
GitHub link: https://github.com/apache/superset/discussions/34357
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] OAuth2 client information for Big query not visible on UI [superset]
Posted by "yj199522 (via GitHub)" <gi...@apache.org>.
GitHub user yj199522 added a comment to the discussion: OAuth2 client information for Big query not visible on UI
I'm not able to see these option while adding new Big Query connection can you help out how can i enable this ?
<img width="480" height="723" alt="Screenshot 2025-07-28 at 11 34 39 AM" src="https://github.com/user-attachments/assets/8da8a0bb-d5d6-49e5-bcb9-3ac61753c42a" />
GitHub link: https://github.com/apache/superset/discussions/34357#discussioncomment-13913017
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org