You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2019/06/30 12:35:00 UTC
[jira] [Updated] (DIRSERVER-1857) Allow registration of an
LdapsInitializer at the LdapServer
[ https://issues.apache.org/jira/browse/DIRSERVER-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1857:
-----------------------------------------
Fix Version/s: 2.0.0
> Allow registration of an LdapsInitializer at the LdapServer
> -----------------------------------------------------------
>
> Key: DIRSERVER-1857
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1857
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.0.0-M12
> Reporter: Achim Willems
> Priority: Major
> Fix For: 2.0.0
>
>
> Due to a BSI directive we need mutual authentication for SSL/TLS connections. BSI (Bundesamt für Sicherheit in der Informationstechnik) is a german governmental organization. This means, that we cannot ignore this directive.
> The current implementation of org.apache.directory.server.ldap.LdapServer uses the static method org.apache.directory.server.ldap.handlers.ssl.LdapsInitializer.init to initialize the SSL communication.
> It would be helpful to have an LdapsInitializer interface with a default implementation (i.e. the current implementation is the default) and the possibility to register this interface at the LdapServer.
> We then could implement our own version of the initializer to establish the necessary behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org