LDAP bind using the userpassword attribute value

Question

I'm trying to prove that I can bind to OID using an SHA password digest, so I'm binding as follows:
./ldapbind -h ipaddress -p myport -D cn=myuser,cn=users,dc=xxxx -w myuserspassword
This works fine if I enter the cleartext password. What I want to do is enter the password as it appears in the users 'userpassword' field, which is an SHA digest.
So if the password is 'abcdef', the userpassword value is something like {SHA}cGsjdkGsgfd.
So, -w abcdef works fine, but how can I do something like -w cGsjdkGsgfd and tell OID it's an SHA digest I'm using?
What I'm ultimately trying to do is to get a SOAP request to authenticate my user against OID and the only password available to it is the SHA digest. It's failing and I don't know why, so my first step is trying to prove I can bind with the password digest.
Thanks in advance.

Answer 1

Yes, sorry about that - I started off trying to prove a potential solution.
Aim:
A user logs onto a weblogic application and is authenticated against OID. The application is making SOAP service calls to a proxy endpoint monitored by another vendors software which authenticates the user against the ldap and checks their roles to see if the user can call the service.
Solution so far:
The initial application gets the username from the JAAS principal, but the password is not supplied. I can easily supply the SHA password digest to it (but putting a cleartext password in the header will probably not be given the go-ahead). This would enable the application to make the SOAP call with a username and digest.
The software protecting the services can be configured in a variety of ways to authenticate the user to the ldap. One involves using the wsse username token in the header (cleartext password or digest).
This authentication is failing and I don't yet have the diagnostic tools available to see which stage is in error. I was trying to prove that you could actually authenticate with an SHA password digest by doing a bind.
Regards