Closed geoffritter closed 4 years ago
I don't now have an active test setup, but does it use it from env any more if you change it from the GUI? I'd suspect it's stored into DB after that. So it's probably enough to add text into README that it's only setup password, and if used for anything else than development, one should change it from GUI.
The user recreates it self with whatever is set in the /etc/containers/pod/awx.yaml file and restarting the pod. I was able to stop this by commenting out both instances of the user/pass parameters.
On Tue, Apr 14, 2020, 12:13 PM Ilkka Tengvall notifications@github.com wrote:
I don't now have an active test setup, but does it use it from env any more if you change it from the GUI? I'd suspect it's stored into DB after that. So it's probably enough to add text into README that it's only setup password, and if used for anything else than development, one should change it from GUI.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ikke-t/awx_pod/issues/11#issuecomment-613630551, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIV3ZWAS4FQXTVFSEXDJWLRMSYVVANCNFSM4MH3DIBA .
The admin user/password defined at deploy time persists through restarts, this might be an unintended security concern for some users.