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-41100: DB2 Gives an Error When a Local User Connects to the Database on Red Hat 8.2

Authentication Service ,  

16 September,20 at 03:41 PM

Problem:  
   
After the Centrify DB2 username/password plugin is configured on a Red Hat 8.2 host machine, when a local user connects to the database, the following error is seen in the shell:
  
SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

  
The following error can also be seen in the centrifydc.log debug log:
  
adclient[1706129]: DEBUG <fd:18 CAPIAuthValidatePlainTextUserNonCDC2 > util.cmdexec '/usr/share/centrifydc/sbin/cdc_chkpwd' exited with status 2
  
adclient[1706129]: DEBUG <fd:18 CAPIAuthValidatePlainTextUserNonCDC2 > base.except Module=Base : Invalid credential to do non-cdc authentication for user: db2locu2. (reference ipcclient.cpp:291 rc: 1030)
  
adclient[1706129]: DEBUG <fd:18 CAPIAuthValidatePlainTextUserNonCDC2 > base.except Module=Base : Invalid credential to do non-cdc authentication for user: db2locu2. (rc: 1030)
  
adclient[1706129]: DEBUG <fd:18 CAPIAuthValidatePlainTextUserNonCDC2 > daemon.ipcclient2 request 'CAPIAuthValidatePlainTextUserNonCDC2' complete

 
Cause:
 
The Centrify supplied command, /usr/share/centrifydc/sbin/cdc_ckhkpwd, requires the Centrify kerberos libraries.  The error occurs when Centrify libraries are not first in the LD_LIBRARY_PATH.
  
 
Workaround:
  
1) Login as root
2) Rename "/usr/share/centrifydc/sbin/cdc_chkpwd" to "/usr/share/centrifydc/sbin/cdc_chkpwd.orig"
3) Add a wrapper script /usr/share/centrifydc/sbin/cdc_chkpwd. For Linux x86_64:
 
#!/bin/sh

LD_LIBRARY_PATH=/usr/share/centrifydc/lib64:/usr/share/centrifydc/kerberos/lib64
export LD_LIBRARY_PATH
exec /usr/share/centrifydc/sbin/cdc_chkpwd.orig
  
4) Change the permissions of the wrapper script to 0755

  
Solution:

This issue will be addressed in Centrify Authentication Service (adclient) release 2020.1 

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

Related Articles

 articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-6041: How to show current license type in use by adclient articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-3925: How to add Centrify parameter to a group policy article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I