directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ute Schröder (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (DIRSERVER-1841) keystore password cannot be set
Date Tue, 07 May 2013 14:15:16 GMT

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

Ute Schröder resolved DIRSERVER-1841.
-------------------------------------

    Resolution: Not A Problem

I don't understand it, but the SSL connection works fine even though my keystore is password-protected
and I can't set the keystore password in the ldapServer.
So I guess this bug is not really a bug. Sorry about that. 
                
> keystore password cannot be set
> -------------------------------
>
>                 Key: DIRSERVER-1841
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1841
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M11
>         Environment: MAC OS-X, java version "1.6.0_45"
>            Reporter: Ute Schröder
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> it looks like I cannot specify a keystore password for the keystore that contains the
SSL Certificate I want to use with my ldap server. There's only an option to speficy the certificate
password: LdapServer.setCertificatePassword(String)
> but none for the keystore password. 
> Also, in LdapServer.java, the keystore is always loaded with null as the keystore password
(LdapServer.loadKeyStore() method). 
> I can circumvent this problem by specifying keystore and password on the command line/in
the system properties like this: 
> -Djavax.net.ssl.keyStore=mykeystore.ks -Djavax.net.ssl.keyStorePassword=secret
> but since this overrides the VM-wide keystore settings, it would be better if it could
be set it specifically for the LdapServer.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message