directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-965) Enabling ldpas via bean configuration fails (connection refused from a client's point of view)
Date Sun, 10 Jun 2007 20:44:26 GMT


Stefan Zoerner commented on DIRSERVER-965:

Perhaps we can make it easier for users if the the line

<property name="enableLdaps" value="true" /> 

is included in the default server.xml for the ldapsConfiguration configuration bean. ldaps
would be disabled by default anyway, but others will not have the same problems to figure
out that this property has to be added.

> Enabling ldpas via bean configuration fails (connection refused from a client's point
of view)
> ----------------------------------------------------------------------------------------------
>                 Key: DIRSERVER-965
>                 URL:
>             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
> 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="">
>     <!-- 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.

View raw message