Looks good, committed.

Ok.  How about this patch?  If no password expiration is setup, then 
$tuple was something like this:



Array([user_uid] => 'username' [user_pass] => 'password' [] => )



So,  Horde_SQL::updateValues() was returning a " = NULL "  for that 
third element, causing the SQL error.



Now check for existence of 'soft_expiration_field' before setting the 
$tuple element to Null.



(Also added the __FILE__ and __LINE__ params to the log call)

Your patch makes it impossible to change an existing expiration date 
to "no expiration". I've added code to log any errors in that 
function, and I've made some changes to Horde_SQL::updateValues() that 
might fix things for you - let me know what you see now.

I believe this patch will take care of the issue.   When the backend 
is not using password expiration, I don't see any reason why we would 
have to set  these values to null instead of just leaving them unset.   
I'm not very familiar with the Auth code though, so please correct me 
if I'm wrong...

Resetting / changing passwords fails under user administration with a 
DB Error: Syntax error.   I'm using mysql for authentication.  I can't 
find any log messages in the log that are coming from the 
attempt...This works fine in the FRAMEWORK_3 branch for me though.