Page 1 of 1
Autologin not working
Posted: Wed Jun 12, 2024 4:32 am
by Tadej_Vretic
Hello,
for a customer I had to migrate nagios from CentOS to Redhat.
I did a new install on Redhat and than restored a backup from CentOS.
On the old system we had a readonly user used for autologin, but since I migrated that autologin isnt working anymore.
I checked the autologin setting and it is active and the right user is selected.
Re: Autologin not working
Posted: Wed Jun 12, 2024 9:07 am
by gwesterman
Hi @Tadej_Vretic,
Is the auto-login button appearing or not? If it is, do you get any errors in the console or any php errors when you click it? Can you try making a new user and setting that user as the auto-login? And look for any relevant errors during this process as well.
Please let us know what you find.
Thank you!
Re: Autologin not working
Posted: Mon Jun 17, 2024 10:34 pm
by lindgren
Look into manually configuring autologin for the read-only user on Red Hat. This likely involves editing files like /etc/inittab or using graphical login managers like LightDM or GDM.
Check the restored configuration files related to autologin (e.g., /etc/inittab) and see if they are compatible with Red Hat. You might need to adjust them for Red Hat's specific syntax.
Re: Autologin not working
Posted: Tue Jun 18, 2024 3:27 am
by Tadej_Vretic
Hi @gwesterman,
yes, the autologin is there, tried to create a new user and assign it as autologin user but it still doesnt work.
If I press the autologin button I get the error invalid username or password.
To me it looks like the autologin button is the sam as login, because if I enter the credentials and click on autologin it logs me in as that user.
It worked on 5.8.10 but not on 2024R1.1.4.
Re: Autologin not working
Posted: Tue Jun 18, 2024 7:05 am
by Tadej_Vretic
Have further info on the issue.
If I switch locale at the login screen to english the auto login works.
Re: Autologin not working
Posted: Tue Jun 18, 2024 9:13 am
by gwesterman
Hi @Tadej_Vretic,
It looks like you have found a bug! I can replicate this and will file an internal ticket. Keep an eye on our
changelog for the fix.
Thank you for the report!