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

Global OAuth Configuration #140

Closed
williambargent opened this issue Jun 16, 2016 · 3 comments
Closed

Global OAuth Configuration #140

williambargent opened this issue Jun 16, 2016 · 3 comments

Comments

@williambargent
Copy link
Member

williambargent commented Jun 16, 2016

Expected behaviour

When configuring OAuth for Google Drive and Dropbox the Client ID and Secret Key should be set once in the /config/config.php file. This is so all users use a single API and the secret key doesn't need to be shared with users or the need to create their own.

Actual behaviour

Each user who wants to mount one of these locations need to provide a client ID and secret key.

@MorrisJobke
Copy link
Member

This is what the global auth configuration in ownCloud EE did for some external storage providers.

@blizzz Maybe we could build this in a way, that every external storage benefits from it ;)

@williambargent
Copy link
Member Author

williambargent commented Jun 17, 2016

It think it should also be in the SE, many users won't know what/how to obtain this. The admin should and will then be able to manage it for the whole installation. Would make life simpler for sysadmin's.

@MorrisJobke
Copy link
Member

This would mean that you run faster in the rate limiting of the services. Additionally it doesn't look like this is possible anyways in the future, because they look down more and more - ref #5815

As of now there is no plan to do this in config.php. If at all this should happen in a dedicated app only responsible for the specific storage.

I will close this here for now.

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

No branches or pull requests

2 participants