[RADIATOR] "Bad Encrypted password" - Authby LDAP2 and Active Directory

Bob Rotsted rrotsted at pdx.edu
Tue Sep 14 12:11:25 CDT 2010


Hi all,

I'm attempting to use Authby LDAP2 to proxy authentication requests to
our active directory server with the "ServerChecksPassword" switch.

Everything appears to be working correctly -- binding completes, etc --
until the user's password is verified. When AD checks the user's
password, Authby LDAP2 throws the following errors:

Tue Sep 14 09:46:48 2010: DEBUG: Radius::AuthLDAP2 looks for match with
user [user]
Tue Sep 14 09:46:48 2010: DEBUG: Radius::AuthLDAP2 REJECT: Bad Encrypted
password: user [user]
Tue Sep 14 09:46:48 2010: INFO: Connecting to 131.252.0.0:636
Tue Sep 14 09:46:48 2010: INFO: Attempting to bind to LDAP server
131.252.0.0:636
Tue Sep 14 09:46:48 2010: DEBUG: No entries for DEFAULT found in LDAP
database
Tue Sep 14 09:46:48 2010: DEBUG: AuthBy LDAP2 result: REJECT, Bad
Encrypted password
Tue Sep 14 09:46:48 2010: INFO: Access rejected for user: Bad Encrypted
password

My current configuration works on another server, perhaps my new server
is missing a library? Anyone else experiencing this issue?

Best,

-- 
Bob Rotsted

Network Security Analyst
Portland State University
Desk: 503-725-6215
Cell: 503-208-6575
314B D581 A8CD E28A A690 7E9D 5B43 4B28 0EB6 A21A


More information about the radiator mailing list