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-6664: LDAP Proxy fails to find partially defined profiles in child zones.

29 April,16 at 02:31 PM

Applies to: 

Centrify LDAP Proxy 5.3.0 

Question: 

LDAP Proxy does not return user information if the user's UNIX name and UID are defined in parent zone only. Error message received is "No such object (32)" and "adquery user <user_name>" returns the user's information correctly. 
 
[root@definitely.not.isis ~]# adquery user sarcher
sarcher:x:1879049332:1879049332:Sterling Archer:/home/sarcher:/bin/bash

[root@definitely.not.isis ~]# ldapsearch -LLL -D sarcher@not.isis -w ants  -H ldap://$(hostname -f)  "(&(objectClass=posixAccount)(uid=sarcher))"
No such object (32)

      Description

Answer: 

There is a bug with LDAP proxy where it incorrectly skips the user's serviceConnectionPoint object when the user's UID and UNIX name are not defined in the child zone.
This issue is fixed in Server Suite 2016.1. 
As a workaround, please create a complete user profile in the child zone. 
 

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