Sorry for the delay.
There is a way to access sockets by registering a socket creation listener. See Section 18.104.22.168 "Socket creation listeners" of the Remoting Guide: http://http://docs.jboss.org/jbossremoting/2.5.4.SP3/guide/html/ .
Hope that helps.
Thank you for your reply.
We have already tried using a handshake complete listener to check the certificate offered by a client during SSL handshake. Nevertheless, we cannot see a way to determine which SSL connection is the source of an invocation received by the server. This does not seem to be an issue for later versions of JBoss Remoting.because we could then use invocationRequest.getRequestPayload().get(Remoting.CLIENT_ADDRESS).
We do anticipate upgrading to a later version of JBoss in the near future, so perhaps we will need to revisit this problem when that upgrade is complete.