-
☆ A M B ☆
- 2,475 Posts
For some of my Snippets, plugins, etc, I have custom configuration details including database logins... does anyone have a recommended location of storing these? I’m curious to see how others are handling this situation...
Thanks!
-
☆ A M B ☆
- 872 Posts
Oh, i would be very interested in that topic too.
I have a working plugin with Google Analytics and a Custom maanger page with Google Analytics Charts inside the manager. I would really like to release them with some options to store the user/pass for several accounts.
In fact that’s not the only components, the same goes for flickr/picasa accounts.
For my needs, i don’t mind having the account informations in hard code, but to release them to public, i would like a way to store those informations in the setting grid for example.
@splittinred
But how to hide the login/pass informations ?
Is it not a security threat ?
-
☆ A M B ☆
- 2,475 Posts
Yeah... system settings isn’t where I’d want to put database info. If someone somehow compromised my MODx database login information, then they could view the logins to my other databases. Maybe I could just put in my own custom config file alongside the regular one in core/config/
Ah, yes, I misunderstood. You could do it a myriad of different ways, but a custom config file with encrypted data is best.
MODx does not provide this out of the box, however.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
-
☆ A M B ☆
- 872 Posts
Maybe that in future release of Revolution, you could allow password textfield vtype in extjs, and store passwords informations encrypted in MODx db setting field ?