OUD11g - 'oud-Setup --cli --rootUserPasswordFile' on Windows Creates an Invalid Password (Doc ID 2137637.1)

Last updated on DECEMBER 10, 2021

Applies to:

Symptoms

Unable to authenticate to the server after performing scripted setup (Command Line Setup) of OUD Directory using example below command.   Attempting to use dsconfig, ldapsearch or status command[s], even ODSM was failing even when the correct password was provided.

When using dsconfig and providing the same password file path as used when performing oud-setup, then dsconfig / status command works.  Please note this was observed on a Windows platform. Note here password in the file <PWD_FILE> which is "<PASSWORD_EXAMPLE>" is used as an example.

NOTE: The importance is not the file path, it is regarding the password file content. In this case Example password file name was <PWD_FILE>.

Failing Scenario:

Note here password in the file <PWD_FILE> which is "<PASSWORD_EXAMPLE>" for example was given as input for Password prompt in below command and it failed.

C:\$INST_PATH\asinst_4\OUD\bat>status.bat

>>>> Specify Oracle Unified Directory LDAP connection parameters

Administrator user bind DN [cn=<DS_ADMIN>]:

Password for user 'cn=<DS_ADMIN>':
Unable to connect to the server at "HOSTNAME" on port <ADMIN_PORT>

--- Server Status ---
Server Run Status: Started
Open Connections: 0

--- Server Details ---
Host Name: HOSTNAME
Administrative Users: cn=<DS_ADMIN>
Installation Path: C:\$INST_PATH\Oracle_$INST_PATH_2
Instance Path: C:\$INST_PATH\asinst_4\OUD
Version: Oracle Unified Directory 11.1.2.3.0
Java Version: <not available> (*)
Administration Connector: Port <ADMIN_PORT> (LDAPS)

--- Connection Handlers ---
Address:Port : Protocol : State
-------------:----------:---------
-- : LDIF : Disabled
0.0.0.0:161 : SNMP : Disabled
0.0.0.0:<JMX_PORT> : JMX : Disabled
0.0.0.0:<LDAP_PORT> : LDAP : Enabled
0.0.0.0:<LDAPS_PORT> : LDAPS : Enabled

--- Data Sources ---
Base DN: cn=virtual acis
Backend ID: virtualAcis
Entries: <not available> (*)
Replication: Disabled

Base DN: dc=<SUFFIX_DN>
Backend ID: <BACKEND_ID>
Entries: <not available> (*)
Replication: Disabled

* Information only available if you provide valid authentication information
when launching the status command.

Working Scenario:

 Here for the status command instead path to the password file was provided, in which case it works.

C:\$INST_PATH\asinst_4\OUD\bat>status.bat --bindDN "cn=<DS_ADMIN>" --bindPasswordFile c:\$PATH_TO\<PWD_FILE>

--- Server Status ---
Server Run Status: Started
Open Connections: 1

--- Server Details ---
Host Name: HOSTNAME
Administrative Users: cn=<DS_ADMIN>
Installation Path: C:\$INST_PATH\Oracle_$INST_PATH_2
Instance Path: C:\$INST_PATH\asinst_4\OUD
Version: Oracle Unified Directory 11.1.2.3.0
Java Version: 1.7.0_79
Administration Connector: Port <ADMIN_PORT> (LDAPS)

--- Connection Handlers ---
Address:Port : Protocol : State
-------------:----------:---------
-- : LDIF : Disabled
0.0.0.0:161 : SNMP : Disabled
0.0.0.0:<JMX_PORT> : JMX : Disabled
0.0.0.0:<LDAP_PORT> : LDAP : Enabled
0.0.0.0:<LDAPS_PORT> : LDAPS : Enabled

--- Data Sources ---
Base DN: cn=virtual acis
Backend ID: virtualAcis
Entries: 0
Replication: Disabled

Base DN: dc=<SUFFIX_DN>
Backend ID: <BACKEND_ID>
Entries: 12
Replication: Disabled

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.