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

'admin' should be disabled #96

Open
Gustry opened this issue Dec 12, 2017 · 7 comments
Open

'admin' should be disabled #96

Gustry opened this issue Dec 12, 2017 · 7 comments

Comments

@Gustry
Copy link
Contributor

Gustry commented Dec 12, 2017

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.

@lucernae
Copy link
Collaborator

lucernae commented Mar 9, 2018

Yes, this also have been in my mind for so long. The way I propose to solve it (for production instance):

  • keep admin/admin login enabled by default
  • the admin of course should change his password in the first place
  • prevent paver sync from loading sample_admin.json fixtures (where admin/admin login described) so it was not going to reset.

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.

@vasuse7en
Copy link

@lucernae should we use "data migrations" instead of fixtures?

@lucernae
Copy link
Collaborator

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.

@gubuntu
Copy link
Contributor

gubuntu commented May 7, 2018

@vasuse7n would you like to take this on?

@vasuse7en
Copy link

@gubuntu yes i would like too.

@gubuntu gubuntu added the backlog label Sep 3, 2018
@gubuntu
Copy link
Contributor

gubuntu commented Oct 10, 2018

Hi @vasuse7n did you make any progress with this? Have you upgraded recently with our latest work?

@vasuse7en
Copy link

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.

@gubuntu gubuntu removed the backlog label Jul 9, 2019
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

4 participants