OUD - How to Access the cn=monitor Suffix Over the LDAP Port
(Doc ID 1546817.1)
Last updated on AUGUST 09, 2023
Applies to:
Oracle Unified Directory - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Goal
By default, the cn=monitor suffix can only be retrieved via the admin port using SSL, as in the following request -
% ./ldapsearch -h <HOSTNAME> -Z -p <ADMIN_PORT> -D "cn=<DS_ADMIN>" -w <PASSWORD> -b "cn=monitor" objectclass=*
The server is using the following certificate:
Subject DN: CN=xxxxx.<DOMAIN>.com, O=Administration Connector Self-Signed Certificate
Issuer DN: CN=xxxxx.<DOMAIN>.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
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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| A) Command line |
| 1) Create a workflow |
| 2) Attach the workflow to the network-group |
| B) Interactive command line |
| 1) Create a workflow |
| 2) Attach the workflow to the network-group |