Looking For help with Repository creation during the LADP integration with Company AD

[Pratik_More]

Version: Windchill 12.1

Use Case: The current documentation for creating the repository is bit superficial I am not able to get clarity with the suggestions,

Description:

Hell Experts,

I am trying to integrate the company AD LDAP with Windchill.

I have installed WC 12.1 with OpenDJ as directory server and now I am trying to achieve the Company LDAP integration.

I have created the JNDI adaptor and while creating the repository for it the naming and option to be selected is bit confusing.

I am looking for any sort of documentation (with images if possible) about the how the repository created, and other stuff managed. It would be great help. (current documentation is confusing to me as I am not LDAP expert)

if anyone has any sort of personal or custom documentation or any article link it would be great to have it.

I am stuck on the same step since last 3-4 days. 😞 

Thanks,

Pratik More

[Pratik_More]

I am bit confused when we are trying to integrate the external (company LDAP server) and I have to use the HHTP protocol which port to be used. Currently I have used 389 for OpendDJ directory server ( which is default LDAP). And trying to add the Company LDAP details but as mentioned there is whole lot confusion. 

Any help will be greatly appreciated, 

[mmeadows-3]

Hi Prakit,

It is hard to get answers out of US people over the independence day weekend.

What is your corporate LDAP, Active Directory?  If so, the default global catalog ports are 3268 (LDAP) and 3269 (LDAPS).  In general, you don't want to use 389 or 636 with Active Directory.  If you are using LDAPS, you need to add the SSL Certificate of the LDAP server to the Windchill's Java keystore (jssecacerts).

Also, an article with integration details...

https://www.ptc.com/en/support/article/CS29454

[Pratik_More · Accepted solution]

Hi mmeadows-3,

Sorry for the delayed response. Thanks for your suggestion and guidance.

I had call with PTC support and able to resolve the issue. I was missing the format of LDAP repository format and other few things suggested by the PTC support and it worked for me.