How To Access the cn=monitor Suffix Over the LDAP Port With Oracle Unified Directory (OUD) 11.1.2+ (Doc ID 1546817.1)

Last updated on JUNE 18, 2017

Applies to:

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

Goal

 By default, the cn=monitor suffix can only be retrieved via the admin port (by default, 4444, using SSL), as in the following request -

 % ./ldapsearch -h localhost -Z -p 4444 -D "cn=Directory Manager" -w secret12 -b "cn=monitor" objectclass=*
The server is using the following certificate:
    Subject DN:  CN=xxxxx.oracle.com, O=Administration Connector Self-Signed Certificate
    Issuer DN:  CN=xxxxxx.fr.oracle.com, O=Administration Connector Self-Signed Certificate
    Validity:  Tue Apr 02 14:34:51 GMT+01:00 2013 through Thu Apr 02 14:34:51 GMT+01:00 2015
Do you wish to trust this certificate and continue connecting to the server?
Please enter "yes" or "no":yes
dn: cn=monitor
startTime: 20130409133056Z
objectClass: top
objectClass: ds-monitor-entry
objectClass: extensibleObject
cn: monitor
currentTime: 20130418150506Z
vendorName: Oracle Corporation
maxConnections: 337
vendorVersion: Oracle Unified Directory 11.1.2.0.0
productName: Oracle Unified Directory
currentConnections: 51
totalConnections: 52541
upTime: 9 days 1 hours 34 minutes 10 seconds

 

The cn=monitor suffix can also be retrieved with ldapsearch using the configured LDAP port

 

Solution

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