Originally created by @IronD7 on GitHub (Oct 23, 2025).
Check Existing Issues
I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Problem Description
Docker secrets are preferably added to the container via files, in particular for Docker Swarm Secrets where this is the only option.
This was solved for the WEBUI_SECRET_KEY here by introducing WEBUI_SECRET_KEY_FILE, but should also be added for providing OAUTH_CLIENT_SECRET via file.
Desired Solution you'd like
Add an environment variable called OAUTH_CLIENT_SECRET_FILE which accepts the path to a file that holds the Oauth Client Secret. If the OAUTH_CLIENT_SECRET environment variable isn't present, presence of the OAUTH_CLIENT_SECRET_FILE will be checked and the OAUTH_CLIENT_SECRET read from provided location.
Alternatives Considered
No response
Additional Context
No response
Originally created by @IronD7 on GitHub (Oct 23, 2025).
### Check Existing Issues
- [x] I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
### Problem Description
Docker secrets are preferably added to the container via files, in particular for Docker Swarm Secrets where this is the only option.
This was solved for the WEBUI_SECRET_KEY [here](https://github.com/open-webui/open-webui/issues/14754) by introducing WEBUI_SECRET_KEY_FILE, but should also be added for providing OAUTH_CLIENT_SECRET via file.
### Desired Solution you'd like
Add an environment variable called OAUTH_CLIENT_SECRET_FILE which accepts the path to a file that holds the Oauth Client Secret. If the OAUTH_CLIENT_SECRET environment variable isn't present, presence of the OAUTH_CLIENT_SECRET_FILE will be checked and the OAUTH_CLIENT_SECRET read from provided location.
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @IronD7 on GitHub (Oct 23, 2025).
Check Existing Issues
Problem Description
Docker secrets are preferably added to the container via files, in particular for Docker Swarm Secrets where this is the only option.
This was solved for the WEBUI_SECRET_KEY here by introducing WEBUI_SECRET_KEY_FILE, but should also be added for providing OAUTH_CLIENT_SECRET via file.
Desired Solution you'd like
Add an environment variable called OAUTH_CLIENT_SECRET_FILE which accepts the path to a file that holds the Oauth Client Secret. If the OAUTH_CLIENT_SECRET environment variable isn't present, presence of the OAUTH_CLIENT_SECRET_FILE will be checked and the OAUTH_CLIENT_SECRET read from provided location.
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Oct 23, 2025):
Why is this needed?