OUD12c - Passwords for IBM Tivoli Directory are not Synchronized to OUD / DIP Integration with Same Hash
(Doc ID 2532705.1)
Last updated on AUGUST 21, 2019
Applies to:
Oracle Unified Directory - Version 12.2.1.3.0 and later Information in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, DIP Integration
ACTUAL BEHAVIOR --------------- Password synchronization from Tivoli DS to Oracle Unified Directory is working, however the passwords do not have the same hash stored in OUD and it is causing "invalid credentials" error.
EXPECTED BEHAVIOR ----------------------- DIP should Sync the same password / same encryption which Tivoli DS contains.
STEPS ----------------------- The issue can be reproduced at will with the following setup:
Setup: Source Server - Tivoli Directory Server 6.3 Destination Server - OUD 12.2.1.3.0 DIP Version - 12.2.1.3.0
Issue: DIP configured for Syncing the Tivoli Directory Server to OUD 12.2.1.3.0 Passwords synced from TDS to OUD do not have the same hash and hence BIND with TDS password against OUD fails with invalid credentials.
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!