OUD11g - oud-Setup --cli --rootUserPasswordFile On Windows Creates An Invalid Password (Doc ID 2137637.1)

Last updated on JUNE 20, 2016

Applies to:

Oracle Unified Directory - Version 11.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

+. After performing scripted setup (Command Line Setup) of OUD Directory using example below command, unable to authenticate to the server using dsconfig, ldapsearch or odsm, or even status command was failing even though right password was provided.

 

Example :

D:\app\oracle\fmw\Oracle_OUD1\oud-setup --cli --baseDN "dc=oracle,dc=com" --addBaseEntry --ldapPort 2389 --adminConnectorPort 2444 --enableWindowsService --doNotStart --ldapsPort 2636 --generateSelfSignedCertificate --rootUserDN "cn=Directory Manager" --rootUserPasswordFile "c:\OUD11123\Oracle_OUD11123_2\pw1.txt" --serverTuning autotune --importTuning autotune --no-prompt

+. If we use dsconfig and nominate the same password file path as used when performing oud-setup then dsconfig / status command works. Note this was observed on a Windows platform. Note here password in the file pw1.txt which is "Abcxyz2016" is used as an example.

NOTE: Here importance to the file path must not be given and its just about the password file content. In this case Example password file name was pw1.txt.

Failing Scenario:

 

Note here password in the file pw1.txt which is "Abcxyz2016" for example was given as input for Password prompt in below command and it failed.

C:\OUD11123\asinst_4\OUD\bat>status.bat

>>>> Specify Oracle Unified Directory LDAP connection parameters

 

Administrator user bind DN [cn=Directory Manager]:

 

Password for user 'cn=Directory Manager':
Unable to connect to the server at "RCHANNAB-LAP" on port 4444

 

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

 

--- Server Details ---
Host Name: RCHANNAB-LAP
Administrative Users: cn=Directory Manager
Installation Path: C:\OUD11123\Oracle_OUD11123_2
Instance Path: C:\OUD11123\asinst_4\OUD
Version: Oracle Unified Directory 11.1.2.3.0
Java Version: <not available> (*)
Administration Connector: Port 4444 (LDAPS)

 

--- Connection Handlers ---
Address:Port : Protocol : State
-------------:----------:---------
-- : LDIF : Disabled
0.0.0.0:161 : SNMP : Disabled
0.0.0.0:1689 : JMX : Disabled
0.0.0.0:4389 : LDAP : Enabled
0.0.0.0:4636 : LDAPS : Enabled

 

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

 

Base DN: dc=example,dc=com
Backend ID: userRoot
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:\OUD11123\asinst_4\OUD\bat>status.bat --bindDN "cn=Directory Manager" --bindPasswordFile c:\OUD11123\Oracle_OUD11123_2\pw1.txt

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

 

--- Server Details ---
Host Name: RCHANNAB-LAP
Administrative Users: cn=Directory Manager
Installation Path: C:\OUD11123\Oracle_OUD11123_2
Instance Path: C:\OUD11123\asinst_4\OUD
Version: Oracle Unified Directory 11.1.2.3.0
Java Version: 1.7.0_79
Administration Connector: Port 4444 (LDAPS)

 

--- Connection Handlers ---
Address:Port : Protocol : State
-------------:----------:---------
-- : LDIF : Disabled
0.0.0.0:161 : SNMP : Disabled
0.0.0.0:1689 : JMX : Disabled
0.0.0.0:4389 : LDAP : Enabled
0.0.0.0:4636 : LDAPS : Enabled

 

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

 

Base DN: dc=example,dc=com
Backend ID: userRoot
Entries: 12
Replication: Disabled

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms