PAM stack modules are being altered after CA PAMSC installation - how can I tell what was modified?
Release: Component: SEOSU
This is a standard system-auth file after installing CA PIM: #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth required pam_env.so auth required pam_faildelay.so delay=2000000 auth sufficient pam_fprintd.so auth sufficient pam_unix.so nullok try_first_pass auth optional pam_seos.so auth requisite pam_succeed_if.so uid >= 1000 quiet_success auth required pam_deny.so
We add these lines: auth optional pam_seos.so account optional pam_seos.so password sufficient pam_seos.so session optional pam_seos.so
Any additional modifications done to the PAM stack that is outside our out of the box configuration will be treated as customization and cannot be worked under a Support scoping perspective- any customizations that want to be worked on heavily will need a Services engagement.