cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Translate the entire conversation x

Corp LDAP integration with Windchill

AK_10242704
2-Explorer

Corp LDAP integration with Windchill

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.1.4

Our intension is to integrate Corp Active Directory with Windchill. So I followed Article to https://www.ptc.com/en/support/article/CS29454#4 to configure access to an additional LDAP Directory in Windchill. After doing all the steps given in the Article I'm unable to login to the server, I tried to login to wcadmin but still not able to login. Error message shows in log "Nested exception is: wt.org.OrganizationServicesIEException: javax.naming.CommunicationException: corpldap.mydomain.com:389"
ACCEPTED SOLUTION

Accepted Solutions

To configure Windchill with Active Directory, you can refer to article https://www.ptc.com/en/support/article/CS29445.

Per the message "javax.naming.CommunicationException: corpldap.mydomain.com:389", make sure your Windchill machine can connect to your AD server "corpldap.mydomain.com" via the port 389, otherwise, you may try other port like 3268 or check your AD admin.

View solution in original post

3 REPLIES 3

Are you integrating just the webserver or did you also change your ie settings to connect to the same LDAP?

According to PTC, this is a port issue.  Most likely, the port is blocked by firewall.
https://www.ptc.com/en/support/article/CS389562


With Active Directory, use ports 3268 (LDAP) or 3269 (LDAPS).  The generic 389 and 636 ports don't provide access to the global catalog, which is commonly needed for Windchill LDAP integrations.

FYI: It is a recommended practice to validate the corporate LDAP connection information provided by IT in an LDAP client like Apache Directory Studio before integrating.  It is best to know the server can connect to the LDAP server with the provided information before getting into a Windchill configuration debugging session.
 

To configure Windchill with Active Directory, you can refer to article https://www.ptc.com/en/support/article/CS29445.

Per the message "javax.naming.CommunicationException: corpldap.mydomain.com:389", make sure your Windchill machine can connect to your AD server "corpldap.mydomain.com" via the port 389, otherwise, you may try other port like 3268 or check your AD admin.

Announcements

Top Tags