[
https://issues.apache.org/jira/browse/DIRSERVER-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503546
]
Enrique Rodriguez commented on DIRSERVER-965:
---------------------------------------------
I agree with the change you made to address usability here. If we are going to
have a bean for LDAPS then it makes sense to have the LDAPS nature enabled by
default in it.
> Enabling ldpas via bean configuration fails (connection refused from a
> client's point of view)
> ----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-965
> URL: https://issues.apache.org/jira/browse/DIRSERVER-965
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: * ApacheDS 1.5.1 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Assignee: Stefan Zoerner
>
> If I try to enable ldaps in a standalone server (freshly installed) via the
> bean configuration file (server.xml) like this:
> <bean id="ldapsConfiguration"
> class="org.apache.directory.server.ldap.LdapConfiguration">
> <!-- Whether to enable the LDAPS protocol.
> -->
> <property name="enabled" value="true" />
> <!-- The port to run the LDAPS protocol on.
> -->
> <property name="ipPort" value="636" />
> <property name="ldapsCertificateFile"
> value="C:/java/apacheds-1.5.1-SNAPSHOT/conf/zanzibar.ks" />
> <property name="ldapsCertificatePassword" value="secret" />
> </bean>
> the server starts, but only listens on 10389 (plain LDAP). Connection on 636
> are still refused by the server. There are no relevant lines in the log file,
> even with DEBUG level.
> ldaps is certification relevant for the Open Group, hence this is a blocker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
