-
Notifications
You must be signed in to change notification settings - Fork 12
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
Hardcoded Secrets #13
Comments
Hardcoded secrets are only for testing purposes. The management of secrets is a responsibility of a libcloudstorage client. cloudstorage-fuse (being a libcloudstorage client) currently doesn't load secrets from elsewhere. |
I'm trying to figure this out but can't. Rephrasing your words might highlight my confusion:
If this is the case, where does cloudstorage-fuse load its secrets from that it is responsible for? I can't locate any secrets under |
cloudstorage-fuse doesn't load secrets from anywhere which means that it just uses the default hardcoded secrets. Loading from other place is not currently implemented in cloudstorage-fuse. |
It seems the OAuth app details are hardcoded into the source. Example 1 Example 2.
Can this be changed to use a central config source (like in cloudbrowser), and can that config inherit from environment variables, not hardcoded source values that require a recompile?
The text was updated successfully, but these errors were encountered: