On Mon, 2012-04-09 at 12:38 -0700, Sharad Mishra wrote:
> On Mon, 2012-04-09 at 14:10 -0400, Oved Ourfalli wrote:
>>>>
>>>> When a call is made to construct InitialDirContext with following
>>>> settings -
>>>>
>>>> {java.naming.provider.url=ldap://ldapserver.ibm.com:389,
>>>> java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory,
>>>>
java.naming.security.principal=uid=1234567,c=us,ou=ldapserver,o=ibm.com,
>>>> java.naming.security.authentication=DIGEST-MD5 GSSAPI,
>>>> java.naming.security.credentials=password,
>>>> java.naming.referral=follow,
>>>> java.naming.ldap.attributes.binary=objectGUID}
>>>>
>>
>> Can you also attach the jboss log and engine log? (assuming you are testing it in
the ovirt-engine environment).
>> They can be helpful, as it might be related to some class loading issue or
something similar, and the log might shed light on that.
>>
>
I think its my setup that is the issue here. I am unable to run
ldapsearch CLI with DIGEST-MD5 protocol. I am not sure how to setup/use
secret key with sasl. I am running my queries against a production ldap
server on which I have user access. I tried to look around on internet
but did not get a good hit.
have you tried the kebreros based authentication with it?
I see it is supposed to have it: