Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1259399202.539581269823167281.JavaMail.jira@brutus.apache.org>
Date: Mon, 29 Mar 2010 00:39:27 +0000 (UTC)
From: "Matt Doran (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Created: (DIRSERVER-1489) Provide access to remote
 connection info
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Provide access to remote connection info
----------------------------------------

                 Key: DIRSERVER-1489
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1489
             Project: Directory ApacheDS
          Issue Type: Improvement
    Affects Versions: 1.5.5
            Reporter: Matt Doran


I'm developing a custom partition and custom authentication handler to plug into ApacheDS, and need to know the connection details of the client performing the requests.    A reason why this might be useful it to be able to log the source of invalid authentication requests.  

The CoreSession object has a getClientAddress() method, however it always returns null.  The CoreSession object is accessible from the places where it would be useful (i.e. via the context objects passed into the Partition methods ... and also in the AuthenticationInterceptor.)   Upon further investigation it looks like the implementation in DefaultCoreSession is hard-coded to return null.  :(

It also appears that the services main CoreSession object is reused alot (e.g. in the authentication interceptor we use the same session object no matter who the caller is).

I was interested in putting in a short-term patch to work-around this issue while a longer term solution was considered.  But I couldn't find anything obvious.   I'd think it would make sense to stuff the client address into the session somewhere up in one of the protocol handlers (e.g. LdapRequestHandler.handleMessage) ... but there currently isn't anywhere to put this info.  Any ideas on a short-term (even if hacky) way to achieve this?


(raising as requested by Emmanuel Lecharany on user's list)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.