-
Notifications
You must be signed in to change notification settings - Fork 22
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
'admin' should be disabled #96
Comments
Yes, this also have been in my mind for so long. The way I propose to solve it (for production instance):
IMO, it is still a good way to provide default password for admin for first install. We can put the password in rancher catalog, but because this is not an application settings (a user settings), I think we should not put it there. |
@lucernae should we use "data migrations" instead of fixtures? |
This fixtures is Geonode's convention to prepare initial data. We will just have to make sure that some fixtures won't run twice if db already populated. |
@vasuse7n would you like to take this on? |
@gubuntu yes i would like too. |
Hi @vasuse7n did you make any progress with this? Have you upgraded recently with our latest work? |
No @gubuntu. I didn't upgrade with your latest updates. I will try to update this week and look into this issue. Also if there exists a public channel for geosafe in Kartoza slack channel, could you please share me the link? just for easy communication. |
CMIIW but the admin/admin login is always enabled by default.
I think it would be better to not provide an admin login by default. It should either a prompt in the ansible script for the login/password. I don't know if you can do that from rancher catalog.
The text was updated successfully, but these errors were encountered: