You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "devikaaaa33 (via GitHub)" <gi...@apache.org> on 2025/07/15 07:33:54 UTC
[I] oauth details are not fetched by superset applications automatically [superset]
devikaaaa33 opened a new issue, #34164:
URL: https://github.com/apache/superset/issues/34164
### Bug description
Hi, I am configuring OAuth with Superset. I have stored the client ID, password, and all related information in the Terraform vault. Is this application capable of fetching these details from tf-vault automatically and restarting the application when changes are detected?
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] oauth details are not fetched by superset applications automatically [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #34164: oauth details are not fetched by superset applications automatically
URL: https://github.com/apache/superset/issues/34164
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] oauth details are not fetched by superset applications automatically [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #34164:
URL: https://github.com/apache/superset/issues/34164#issuecomment-3072445300
<!-- Answer -->
Superset does not natively support automatically fetching OAuth credentials (like client ID and secret) from Terraform Vault or any external secret manager at runtime, nor does it have a built-in mechanism to detect changes in those secrets and restart or reload itself when they change. Superset loads all configuration, including OAuth credentials, at application startup from environment variables or static config files (such as superset_config.py). While you can write custom Python logic in superset_config.py to fetch secrets from an external source at startup, this is not dynamic—any changes to secrets require an external process (like your orchestration tool or deployment pipeline) to update the config and restart Superset for changes to take effect. There is no built-in documentation or feature for dynamic secret fetching or automatic reloads in response to secret changes in the current codebase or docs ([reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b4
3b1ed3b063ffe45377799c/superset/config.py)).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/45dcb4b6-0aea-44de-9873-d279a4ccf92d?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [!
[Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34164)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org