Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-10036: Does SLES 12 (SP2) still using Apparmor as Linux Kernel Security module?

Authentication Service ,  

19 March,18 at 06:10 PM

Problem:  Why SLES 12 (SP2)  is still using Apparmor as Linux Kernel Security module?

Cause:  It appears Apparmor is still enabled in pam.d entries.

Example:
======================================================== 
/etc/pam.d/dzdo-ad-mfa:
#%PAM-1.0
auth     include    common-auth
account  include    common-account
password include    common-password
session  required   pam_limits.so
session  optional   pam_apparmor.so <=====

/etc/pam.d/dzdo-mfa:
#%PAM-1.0
auth     include    common-auth
account  include    common-account
password include    common-password
session  required   pam_limits.so
session  optional   pam_apparmor.so <=====

/etc/pam.d/dzdo:
#%PAM-1.0
auth     include    common-auth
account  include    common-account
password include    common-password
session  required   pam_limits.so
session  optional   pam_apparmor.so <=====
========================================================
Workaround: Comment out all the pam_apparmor.so.

Resolution: It will be fixed in the future release. 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-1956: SQL30082N Security processing failed with reason "15" ("Processing Failure"). articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal?