This is the command I found in my /var/log/messages. It is invoked by realmd during the accounts provider installation
/usr/bin/sh -c /usr/sbin/authconfig --update --enablesssd --enablesssdauth --enablemkhomedir --nostart && /usr/bin/systemctl enable oddjobd.service && /usr/bin/systemctl start oddjobd.service
Before executing it open a spare shell to prevent being locked out of your system!
Have I to modify my authconfig files as your one?
I only made a backup of authconfig, I have not modified anything yet
No, just execute that command! Then you could compare the files to see what it did…
I think we’re in right way.
After your command, my /etc/sysconfig/authconfig is
[root@server ~]# cat /etc/sysconfig/authconfig
CACHECREDENTIALS=yes
FAILLOCKARGS=“deny=4 unlock_time=1200”
FORCELEGACY=no
FORCESMARTCARD=no
IPADOMAINJOINED=no
IPAV2NONTP=no
PASSWDALGORITHM=sha512
USEDB=no
USEECRYPTFS=no
USEFAILLOCK=no
USEFPRINTD=no
USEHESIOD=no
USEIPAV2=no
USEKERBEROS=no
USELDAP=no
USELDAPAUTH=no
USELOCAUTHORIZE=yes
USEMKHOMEDIR=yes
USENIS=no
USEPAMACCESS=no
USEPASSWDQC=no
USEPWQUALITY=yes
USESHADOW=yes
USESMARTCAR=no
USESSSD=yes
USESSSDAUTH=yes
USESYSNETAUTH=no
USEWINBIND=no
USEWINBINDAUTH=no
WINBINDKRB5=no
And it seems like your!
…and now?
Now I can access in eJabberd admin webpage and in pidgin like jabber client! Yesss!!!
Have I to save something?
It’s all ok: authconfig writes the required config files.
I didn’t understand why it failed.
Please, make sure the configuration survives after rebooting the system.
Ok, at this time I can’t reboot the server, but I can do it tomorrow morning!
I restarted the server, and the configuration survives after rebooting!
Thanks a lot Davide! I owe you a beer!!!
You’re welcome!
Please set the solution