directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hendy Irawan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-863) Add SASL DIGEST-MD5 mechanism support
Date Sat, 08 Oct 2011 03:59:29 GMT

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

Hendy Irawan commented on DIRSERVER-863:
----------------------------------------

I am not able to make this work.

CRAM-MD5 works fine on me (both SSL and non-SSL), but DIGEST-MD5 always fails.

ldapsearch -H ldap://***:10389 -Y DIGEST-MD5 -N '(uid=rumahmufida)' 
SASL/DIGEST-MD5 authentication started
Please enter your password: 
SASL username: myuser
SASL SSF: 128
SASL data security layer installed.
# extended LDIF
#
# LDAPv3
# base <ou=clients> (default) with scope subtree
# filter: (uid=rumahmufida)
# requesting: ALL
#

ldap_result: Can't contact LDAP server (-1)

Note: In my command above, most client config is set in ~/.ldaprc

Is DIGEST-MD5 support currently broken, or there's something I should set?
                
> Add SASL DIGEST-MD5 mechanism support
> -------------------------------------
>
>                 Key: DIRSERVER-863
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-863
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>            Reporter: Enrique Rodriguez
>            Assignee: Enrique Rodriguez
>            Priority: Minor
>             Fix For: 1.5.1
>
>
> The main decisions here are around configuration and the mapping of username+realm to
DN.
> The Java SASL API Programming and Deployment Guide
> http://java.sun.com/j2se/1.5.0/docs/guide/security/sasl/sasl-refguide.html
> Java interface javax.security.sasl.SaslServer
> http://java.sun.com/j2se/1.5.0/docs/api/javax/security/sasl/SaslServer.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message