Install Guide
On Red Hat Enterprise Linux 6, for the sblim-sfcb and openwsman to start automatically after a reboot you need to change the run-levels
using the chkconfig utility. For example, if you want to run sblim-sfcb in run-levels 3 and 5, use the following command:
#chkconfig sblim-sfcb on --level 35
NOTE: For more information about chkconfig and its usage, see the operating system documentation.
The managed system is congured and is ready to be used by the Server Administrator Web Server.
Winbind conguration for openwsman and sfcb for Red Hat
Enterprise Linux operating systems
Perform the following to congure openwsman and sfcb:
1 Back up these les:
• /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 the following:
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 the following:
%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
Work around 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, 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: if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, 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
14
Preinstallation Setup