Enrique Rodriguez a écrit :
I have SASL working; that is to say, the DIGEST-MD5, CRAM-MD5, and
GSSAPI mechanisms.
Great ! This is one excellent news !
The integration tests just completed (27 minutes
on a POS box). New SASL integration tests are also complete. I used
the JDK's JNDI
Alex Karasulu wrote:
Stefan Zoerner last year hooked up a way to use digested passwords in the
userPassword field I think. I wonder if there could be issues with SASL
and
this mechanism if the password value in the entry is already really a digest
rather than the password itself in plain
Hi Stefan,
Thanks for chimming in with the additional info. It might come in handy for
what Enrique is working on.
Alex
On 3/6/07, Stefan Zoerner [EMAIL PROTECTED] wrote:
Alex Karasulu wrote:
Stefan Zoerner last year hooked up a way to use digested passwords in
the
userPassword field I
On 3/6/07, Alex Karasulu [EMAIL PROTECTED] wrote:
...
So basically this handles the client side generation of the digest which is
sent to the server rather than the password itself, then the server compares
this digest with the digest generated from the userPassword field?
No, typically a
On 3/6/07, Enrique Rodriguez [EMAIL PROTECTED] wrote:
...
So, based on feedback from you and Emmanuel, I will:
1) Branch the trunk to add SASL.
2) Assign Alex a subtask to add supportedSASLMechanisms in the branch.
An issue is open:
https://issues.apache.org/jira/browse/DIRSERVER-867
3)
Excellent! I'll watch for commits to figure out where your SASL branch is to
add the code to return the supportedSASLMechanisms in the RootDSE.
Alex
On 3/6/07, Enrique Rodriguez [EMAIL PROTECTED] wrote:
On 3/6/07, Enrique Rodriguez [EMAIL PROTECTED] wrote:
...
So, based on feedback from you
I have SASL working; that is to say, the DIGEST-MD5, CRAM-MD5, and
GSSAPI mechanisms. The integration tests just completed (27 minutes
on a POS box). New SASL integration tests are also complete. I used
the JDK's JNDI client to test a variety of positive and negative
scenarios. Also, I tested
