Install Guide
Winbind Configuration For openwsman And sfcb
For Red Hat Enterprise Linux Operating Systems
Follow the instructions mentioned below to configure openwsman and sfcb on 32-bit OMI installation. In case of a 64-bit installation,
replace with .lib lib64
1. Back up these files:
• /etc/pam.d/openwsman
• /etc/pam.d/sfcb
• /etc/pam.d/system-auth
2. Replace the content of /etc/pam.d/openwsman and /etc/pam.d/sfcb with
auth required pam_stack.so service=system-auth
auth required /lib/security/pam_nologin.so
account required pam_stack.so service=system-auth
3. Replace the content of /etc/pam.d/system-auth with
%PAM-1.0
This file is auto-generated.
User changes will be destroyed the next time authconfig is run.
auth required /lib/security/$ISA/pam_env.so
auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok
auth sufficient /lib/security/$ISA/pam_krb5.so use_first_pass
auth sufficient /lib/security/$ISA/pam_winbind.so use_first_pass
auth required /lib/security/$ISA/pam_deny.so
account required /lib/security/$ISA/pam_unix.so broken_shadow
account sufficient /lib/security/$ISA/pam_succeed_if.so uid 100 quiet
account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_krb5.so
account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_winbind.so
account required /lib/security/$ISA/pam_permit.so
password requisite /lib/security/$ISA/pam_cracklib.so retry=3
password sufficient /lib/security/$ISA/pam_unix.so nullok use_authtok md5 shadow
password sufficient /lib/security/$ISA/pam_krb5.so use_authtok
password sufficient /lib/security/$ISA/pam_winbind.so use_authtok
password required /lib/security/$ISA/pam_deny.so
session required /lib/security/$ISA/pam_limits.so
session required /lib/security/$ISA/pam_unix.so
session optional /lib/security/$ISA/pam_krb5.so
Workaround For The Libssl Issue
If the required library needed by openwsman is present on the system, the autoconf_cim_component.sh script tries to resolve the
libssl.so issue. However, if the library is not present, then the script reports the same. Check if the latest version of the libssl library is
installed on the system and then create a soft link with libssl.so.
For example: On a 32-bit installation, if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, then create soft link
with the latest libssl.so.0.9.8b:
• ln -sf /usr/lib/libssl.so.0.9.8b /usr/lib/libssl.so
• ldconfig
On a 64-bit installation, if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, then create soft link with the latest
libssl.so.0.9.8b:
• ln -sf /usr/lib64/libssl.so.0.9.8b /usr/lib64/libssl.so
• ldconfig
Preinstallation Setup
13