-
Notifications
You must be signed in to change notification settings - Fork 96
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
Optionally load client ID, secret and domain from environment #480
Comments
@Floppy - Thank you for the suggestion on this. We were considering something like this for sensitive data storage like the ones you mentioned. WordPress convention is to define a constant in wp-config.php, rather than a .env file. Would that work for your purposes? Then we don't have to load a separate env-parsing library. |
Tracking progress in #488 |
Yeah, it's probably best to stick to the wordpress standard. We can always use an env loader inside our |
Fixed in #509, merged into |
We have multiple environments that we keep in sync with database backups cloned between them. Obviously this confused the Auth0 plugin as it doesn't have the right credentials any more.
Loading the credentials from the environment in a 12-factor app style would make this a lot easier. Perhaps if the values are blank in the database they could be loaded from the env? Another issue here is the user migration token, which could perhaps be generated in a more stable fashion so it doesn't need to be stored in the database?
The text was updated successfully, but these errors were encountered: