[jira] [Created] (DIRAPI-375) Add TLSv1.3 to default protocols

Stefan Seelmann created DIRAPI-375: -- Summary: Add TLSv1.3 to default protocols Key: DIRAPI-375 URL: https://issues.apache.org/jira/browse/DIRAPI-375 Project: Directory Client API Issue

[jira] [Resolved] (DIRSTUDIO-761) GSSAPI Authentication fails when using ADS LDAP Client API

[ https://issues.apache.org/jira/browse/DIRSTUDIO-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-761. --- Resolution: Fixed This has been fixed in scope of the linked issues and tests

[jira] [Commented] (DIRSTUDIO-1219) Directory Studio doesn't StartTLS before authenticating

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366162#comment-17366162 ] Stefan Seelmann commented on DIRSTUDIO-1219: Changed usage of {{useTls}} flag in the LDAP

[jira] [Resolved] (DIRSTUDIO-1219) Directory Studio doesn't StartTLS before authenticating

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1219. Resolution: Fixed > Directory Studio doesn't StartTLS before authenticating >

[jira] [Commented] (DIRSTUDIO-1220) Directory Studio doesn't use the SASL confidentiality layer after negotiating its use

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366138#comment-17366138 ] Stefan Seelmann commented on DIRSTUDIO-1220: Implemented SASL security layer in the LDAP

[jira] [Resolved] (DIRSTUDIO-1220) Directory Studio doesn't use the SASL confidentiality layer after negotiating its use

[ https://issues.apache.org/jira/browse/DIRSTUDIO-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1220. Assignee: Stefan Seelmann Resolution: Fixed > Directory Studio doesn't

[jira] [Resolved] (DIRSERVER-1670) DIGEST-MD5 authentication mechanism must support encryption

[ https://issues.apache.org/jira/browse/DIRSERVER-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSERVER-1670. Fix Version/s: (was: 2.0.0-RC1) 2.0.0.AM27

[jira] [Resolved] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSERVER-1632. Resolution: Fixed > Setting SASL QoP to 'auth-int' or 'auth-conf' while

[jira] [Commented] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366127#comment-17366127 ] Stefan Seelmann commented on DIRSERVER-1632: Added additional tests using openldap

[jira] [Commented] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366109#comment-17366109 ] Stefan Seelmann commented on DIRSERVER-1632:

[jira] [Updated] (DIRSERVER-1632) Setting SASL QoP to 'auth-int' or 'auth-conf' while connecting using the LDAP API fails and throws a decoder exception

[ https://issues.apache.org/jira/browse/DIRSERVER-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSERVER-1632: --- Fix Version/s: (was: 2.0.0-RC1) 2.0.0.AM27 > Setting SASL