Migrating From authconfig to authselect
Guidance for migrating legacy authentication configuration to authselect.
This topic applies only to Oracle Linux 8.
In Oracle Linux 8, the authselect utility replaced
authconfig that was used in prior releases. Compatibility between the two
utilities is minimal. Thus, migrating to authselect is highly
recommended.
Migrating to authselect requires you to complete several actions,
including the following:
-
Convert scripts.
If you use the
ipa-client-installcommand or therealm joincommand to make the host join a domain, you can remove anyauthconfigcall in any scripts. Otherwise, you need to replace eachauthconfigcall with its matchingauthselectcall. -
Update configuration files.
You must configure files for the various services, including those that apply to the following: Kerberos, LDAP, NIS, SSSD, and Winbind.
-
Enforce password quality restrictions for
authselect.The
pam_pwqualitymodule enforces password quality restrictions for local users. You configure this module in the/etc/security/pwquality.conffile, according to the information that's provided in thepam_pwquality(8)manual page. -
Switch from the
authconfig'scacertdir_rehashtool to the nativeopenssl rehashdirectory command. -
Start the appropriate services.
Depending on the profile you select for the
authselectimplementation, start the service for that profile. If you select thesssdprofile, for example, then you would enable and start the SSSD service.sudo systemctl enable --now sssd
For complete migration instructions and examples, see the authselect-migration(7) manual page. See also the authselect(8) manual page.