[jira] Resolved: (DIRSERVER-1324) In default configuration not possible to connect via LDAP and LDAPS from computers other than the one the server has been started from

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-1324.
------------------------------------------

    Resolution: Fixed

I made a mistake when I ported the network layer from MINA 1.0 to MINA 2.0 : when no address is given, the server was accepting incoming requests from localhost by default. 

I restored the original behavior : no address means the wildcard address .

fixed in http://svn.apache.org/viewvc?rev=751913&view=rev

> In default configuration not possible to connect via LDAP and LDAPS from computers other than the one the server has been started from
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1324
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1324
>             Project: Directory ApacheDS
>          Issue Type: Bug
>         Environment: Windows XP
> Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
> ApacheDS 1.5.5 SNAPSHOT 
>            Reporter: Stefan Zoerner
>             Fix For: 1.5.5
>
>
> If I build ApacheDS from the trunk and create noarch installers, I am able to deploy it and start the server with default server.xml. But it is not possible to connect from computers other than the one the server is started from (localhost). 
> Emmanuel assumes the following (cite from dev mailing list):
> "I have to test it, it seems that MINA 2.0 behaves differently than MINA 1.0. By default, when setting the Acceptor without any parameter, it uses the localHost. Not what you want, probably.
> You can change the address in the TcpTransport configuration for the LdapService :
>    <tcpTransport>
>      <tcpTransport address="<your server address>" port="10389" nbThreads="8" backLog="50"/>
>    </tcpTransport> 
> Can you give it a try ?"
> This workaround works fine. It would be nice if the server.xml has not to be adjusted (as it was before).

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