-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
SetupController#run(): prevent admin auto-login after autoconfig-only setup #29423
Conversation
Allowed edit by maintainers. Shall I resolve the conflicts as well? Does anybody care for this? |
Pointer: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/automatic_configuration.html#automatic-setup (I never heard of autoconfig.php before 🙊 ) Isn’t the autologin on purpose? Where/when is the admin password defined in the autoconfig process? |
Doc says «Any unspecified parameters appear on the “Finish setup” screen when you first launch Nextcloud.», isn’t the autologin for this finish setup step? |
For an incomplete autoconfig – yes. In case of a complete autoconfig no more user input is needed, so NC -see OP 2nd GIF- doesn’t even show a finish setup page, but proceeds. So I'm done with setup once I've created a complete autoconfig and closed VIm. As I'm done I may take a coffee break. If during this coffee break someone opens my NC before me, they're admin. That's not fair.
If e.g. I say so e.g. via Ansible, it has a password generator btw.. See OP 1st GIF. |
Well you actually did not setup anything until Nextcloud is opened, no? This is when the autoconfig is applied. I would take the coffee after checking Nextcloud loads 😛 But yeah I understand the idea, if no more data is needed end the session and force the admin to log in with the configured password from autoconfig. |
In my Ansible I actually worked this around via curl after autoconfig placement. |
… setup Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
8271b3c
to
2452aaf
Compare
As this sounds like a nice feature, the requests for this are quite low. Currently there a no plans to implement such a feature. Thus I will close this ticket for now. This does not mean we don't want this feature, but it is simply not on our roadmap for the near future. If somebody wants to implement this feature nevertheless we are happy to assist and help out. |
But I already implemented it(?) |
No description provided.