OK, one happy hacker here came up with a neater solution which allows adding & modifying local users while Windows Authentication is enabled, and is smart enough to not update the User_code field if the user is a local user.
Edit admin_register.asp at around line 367:
'If blnWindowsAuthentication = False Then .Fields("User_code") = strUserCode
If strMode = "edit" Then
If blnWindowsAuthentication = False Then .Fields("User_code") = strUserCode
Else
.Fields("User_code") = strUserCode
End If |
I think it's worth bug-reporting that without this hack, if Windows Authentication is active the db Fields "User_code" is not handled correctly, giving the 500 Error any time you try to modify a Local User. Irrespective of whether or not this is advised or supported, it is still undersirable and unhandled.
At a minimum this error situation should be handled, but in my view (because I need it!) it would be more flexible to allow mixed authentication, since as far as I can tell there are few risks (no risks?) as long as it's done right...
Topic Options
Post Options
Thanks(0)
