Skip to main content
mflegel6-Contributor
6-Contributor
Jun 16, 2026 12:38 PM UTC
Solved

JNDI not able to find users

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.2.10 After configuration of JNDI adapter with corporate AD no user can be found in participant administration. No error can be seen in log files.
mflegelAnswer
6-Contributor
Jun 18, 2026 6:17 AM UTC

As it turned out it was a misconfiguration in the mapping properties in the Info*Engine. After fixing the property names and restarting Windchill, I was able to find users.

Thanks for the help.

View in thread

3 replies

TomU
TomU23-Emerald IV
23-Emerald IV
Jun 16, 2026 4:15 PM UTC

You probably have it configured to successfully talk to AD (good), but in a way that it does not find anything (bad).  As long as it can talk, it won’t throw any errors, even if it can’t find anything.

  1. Make sure the user accounts exist at the same level as your search base, or deeper if the search scope is set to subtree.
  2. If using a user filter, make sure the user accounts are a member of the group(s) being used by the filter.  
  3. Make sure the user filter (if used) is a security group, not an OU.  The filter does not work if the user accounts are simply in an OU.

It can be helpful to use a 3rd party LDAP tool to visually see what the JNDI adapter is seeing in AD.  I prefer Apache Directory Studio (no installation required), but here are plenty of other tools out there. 

 

It is possible to enable debug logging and see exactly what the JNDI adapter is getting back from each query.  

  • com.infoengine.log DEBUG
  • wt.org.LdapServices DEBUG
  • wt.org.ldapservices.verbose

 

References:

Translate
mflegel6-ContributorAuthor
6-Contributor
Jun 17, 2026 11:24 AM UTC

Thank you for the answer. The configuration is pretty simple and I did it like with previous configurations. No filter is used and with a 3rd party software I am able to find the next folders and users. Search scope is set to SUBTREE.

 

I will try the debug loggers to hopefully find more information or possible errors.

 

Will keep you posted.

Thanks
Kind regards

Translate
Terms & ConditionsAccessibility statement