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-0513: NetCool does not autenticate with AD when direct control is installed

Authentication Service ,  

12 April,16 at 11:26 AM

Problem:

The local user netcool is converted to AD user, and application NetCool fails to verify the user passwd hash.


Cause:

This is because by default AD does not keep Unix password hash.


Workaround:

PAM enable the NetCool application, so the PAM will handle the user authentication.

Here are the steps to enable NetCool to use PAM for authentication:

start netcool with –authenticate PAM

added these entries at /etc/pam.conf:

netcool auth required /usr/lib/security/pam_aix
netcool account required /usr/lib/security/pam_aix
netcool password required /usr/lib/security/pam_aix
netcool session required /usr/lib/security/pam_aix

Related Articles

 articleKB-6040: How to change the license type in use after adclient successful joined to the AD? article[TIPS] A Centrify Server Suite Cheat Sheet articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? article[Labs] Using Centrify MFA to secure AWS WorkSpaces with Simple AD article[HOW TO]Install and setup the Centrify Licensing Service articleKB-6041: How to show current license type in use by adclient articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS article[Labs] Using Centrify+AD+YubiKey to secure UNIX/Linux access with Strong Authentication articleHOWTO: Configure DB2 on Linux to leverage Centrify/AD (PAM stack)