Authentication Priority Issue After Upgrading from Windchill 12.1.2.4 to 13.1.2.0 (OpenDJ Preferred
Version: Windchill 13.1
Use Case: I am experiencing an authentication priority issue after upgrading Windchill from 12.1.2.4 to 13.1.2.0, and I would appreciate advice from anyone who has faced and resolved a similar situation.
Description:
■ Previous Environment (12.1.2.4)
- User information stored in WindchillDS
- Password authentication performed via JNDI adapter, using Active Directory
■ Current Environment (13.1.2.0)
- Replaced WindchillDS with OpenDJ
- Intended configuration is the same as before:
- User information in OpenDJ
- Password authentication by Active Directory via JNDI adapter
■ Problem
With the same configuration applied in 13.1.2.0, OpenDJ is being used for authentication first, instead of Active Directory.
However:
The properties
mapcredentials.admin.adapterswt.federation.org.directoryServices
are identical to the working configuration in 12.1.2.4.
If I remove the OpenDJ-related settings from
<HTTPServer>/conf/conf.d/30-app-Windchill-Auth.conf,
Active Directory authentication works correctly and I can log in.
This suggests that the JNDI adapter configuration is valid, and that the issue is likely related only to authentication order / priority in 13.1.2.0.
■ Request
Has anyone encountered a similar issue where OpenDJ takes authentication priority after upgrading to 13.1.x?
If so, I would greatly appreciate any guidance on how the authentication order can be controlled or corrected in 13.1.2.0.
Thank you in advance for any suggestions.