Howard Chu wrote:
Uwe Werler wrote:
-----Ursprüngliche Nachricht----- Von: Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de
Now at least I have a problem with "reqSession": If you examine accesslog at some later time, those volatile session IDs don't tell you anything anymore (e.g. the host that opened the connection). Could acesslog be modified to add some details from the session (like monitorConnectionPeerAddress, monitorConnectionStartTime)?
RTFM and turn on session logging.
AFAICS object class 'auditBind' does not have any attributes related to the client connection URI or client IP address.
If configured with parameter 'session_track_control' web2ldap sends the Session Tracking Control [1] with each request. This also appears in attribute 'reqControls' of the accesslog and contains the IP address of the client connected to web2ldap. This is only useful if the LDAP client is kind of a gateway though.
Ciao, Michael.