Oh well, worth a shot.
I had a similar problem and ended up in the bowels of the auth code with the
perl debugger to try and figure out the correct params. I also wanted to be
able to hook up to a legacy passwd db and it was a bit tricky to get it
working.
If you want to try this, stick a
You've hit it. You are better than my Teddy bear lately. I wasn't
thinking straight. Since the password is coming from the DB instead
of a user form, it's already in SHA1 so it should be treated for the
sake of authentication as clear since SHA1 != SHA1(SHA1).
Thanks and to Peter for the
I have what I first thought was a gimme (this is only tangentially
related to the questions I asked a few days ago; same app, different
DB and part). Legacy porting of a login with Authenticate where I
already have the user id and everything verified. I have tried many
permutations of
Try
$c-authenticate({ acctid = $user-username,
password = $user-password })
or die RC_403: . $user-username . failed to authenticate;
Regards, Peter
-Original Message-
From: Ashley Pond V [mailto:[EMAIL PROTECTED]
Sent: 22 December 2007 08:08
To:
