[jira] Issue Comment Edited: (DIRSERVER-965) Enabling ldpas via bean configuration fails (connection refused from a client's point of view)

["Stefan Zoerner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRSERVER-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503207 ] 

Stefan Zoerner edited comment on DIRSERVER-965 at 6/10/07 1:40 PM:
-------------------------------------------------------------------

I was able to get it up and running with 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="enableLdaps" value="true" />

    <property name="ldapsCertificateFile" value="C:/java/apacheds-1.5.1-SNAPSHOT/conf/zanzibar.ks" />
    <property name="ldapsCertificatePassword" value="secret" />

  </bean>

But I am not sure, whether enabling it with two switches and a reference to this bean from the configuration is quite handy. Perhaps it is possible to remove the "enabled" property completely. If there is a reference to this bean from the configuration, it is enabled. enableLdapscould be used to determine whether it is ldap or ldaps. Just an idea.


 was:
I was able to get it up and runninf with 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="enableLdaps" value="true" />

    <property name="ldapsCertificateFile" value="C:/java/apacheds-1.5.1-SNAPSHOT/conf/zanzibar.ks" />
    <property name="ldapsCertificatePassword" value="secret" />

  </bean>

But I am not sure, whether enabling it with two switches and a reference to this bean from the configuration is quite handy. Perhaps it is possible to remove the "enabled" property completely. If there is a reference to this bean from the configuration, it is enabled. enableLdapscould be used to determine whether it is ldap or ldaps. Just an idea.

> 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
>            Priority: Blocker
>
> 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.