My Oracle Support Banner

OUD12c - The Hostname of the Backend Server is Incorrectly Identified by the "s_conn" Value in the File Access Logger when the "log-connection-details" is Enabled in OUD Proxy (Doc ID 2893637.1)

Last updated on SEPTEMBER 14, 2022

Applies to:

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

Symptoms

With "log-connection-details" the s_conn value in OUD Proxy access logs do not always show "hostname" of backend server

 

Normal behavior:

[2022-05-30T14:28:50.729+02:00] [OUD] [TRACE] [OUD-24641552] [PROTOCOL] [host: <backend_hostname>] [nwaddr: <IP>] [tid: 70] [userId: <OS_USER>] [ecid:<ecid>,0:1] [category: PROXY_REQ] [conn: 3] [op: 1] [msgID: 2] [client: <ip>:<port>] [server: <ip>:<port>] [protocol: LDAP] [bindDN: cn=<DS_ADMIN>] [filter: "(objectClass=*)"] [s_credmode: use-client-identity] [scope: "base"] [s_conn: <OUD_BACKEND_HOSTNAME>:<PORT>] [s_msgid: 3] [base: "<base_dn>"] [attrs: "ALL"] SEARCH

Note: [s_conn: <OUD_BACKEND_HOSTNAME>:<PORT>]

Abnormal behavior: 

[2022-05-30T14:30:17.239+02:00] [OUD] [TRACE] [OUD-24641552] [PROTOCOL] [host: <backend_hostname>] [nwaddr: <IP>] [tid: 162] [userId: <OS_USER>] [ecid: <ecid>,0:1] [category: PROXY_REQ] [conn: 0] [op: 1] [msgID: 2] [client: <IP>:<port>] [server: <IP>:<port>] [protocol: LDAP] [bindDN: cn=<DS_ADMIN>] [filter: "(objectClass=*)"] [s_credmode: use-client-identity] [scope: "base"] [s_conn: 2] [s_msgid: 3] [base: "<base_dn>"] [attrs: "ALL"] SEARCH

Note: [s_conn: 2] <-- No hostname and port

Changes

 Enabled log-connection-details on one file access logger

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!

In this Document
Symptoms
Changes
Cause
Solution
References


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