[
https://issues.apache.org/jira/browse/DIRSERVER-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Karasulu closed DIRSERVER-1189.
------------------------------------
Resolution: Fixed
Implemented for 1.5.3 in commit 669253 here:
http://svn.apache.org/viewvc?view=rev&revision=669253
Because the bigbang has a completely new protocol-ldap module this will be
implemented differently and the implementation will be much simpler.
Regardless though the test case was moved over to the bigbang where 1.5.4 will
be released from here so this issue is fixed accordingly in that branch as well.
http://svn.apache.org/viewvc?view=rev&revision=669254
> Configuration option for confidentiality: requiring TLS secured connections
> for performing requests
> ---------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1189
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1189
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: ldap
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 1.5.3
>
>
> Enable LdapServer with configuration parameter to enforce confidentiality
> requirements when confidentiality required flag is set. This requires
> changes to the handlers to enforce this configuration setting when requests
> come in. The config setting needs to be checked as well as the IoFilterChain
> to see if the sslFilter is engaged. This should allow a simple check to see
> if the confidentiality requirement is satisfied. This approach should work
> for both StartTLS and LDAPS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
