New patch 2003-01-23-23-55-04 PENDING.

A patch was submitted to the patch system:
by a user rcave at host lxwdev-1.schwabfoundation.org
This patch is now in the PENDING state and 
needs to be checked in (committed) 

For this you need to log on to the server and execute
the following commands in the xaraya-patches repository:
1. cd PENDING
2. bk sfiles -x | bk new -
3. bk commit
4. bk push

This will change the state of the patch to REGISTERED
it wil *NOT* apply the patch. Alternatively, you may
wait for the next run of the cron job which will 
automatically check in PENDING patches.

Once a patch is in the REGISTERED state it will be 
propagated by push/pull operations and patch handling
can be done remotely from that point on in any clone
from the main repository once properly synchronized.

Patch system status:
---------------------------------------------
PENDING   :       2
REGISTERED: 7
---------------------------------------------

The patch contains the following changesets:

ChangeSet
  1.447 03/01/23 15:50:14 rcave-rIoA2dxFqdxvvToxOdHx6mP8kLm7lcA4hIvA6WVW+J8@public.gmane.org +3 -0
  Made changes to the user login due to login failing to allow a 
   user that may be trying to login with an external authentication
   module.  Also fixed a minor bug when updating a user as admin.  
  More detailed information is included in deltas.

  html/modules/users/xaruser.php
    1.46 03/01/23 15:50:13 rcave-rIoA2dxFqdxvvToxOdHx6mP8kLm7lcA4hIvA6WVW+J8@public.gmane.org +58 -9
    users_user_login() did not allow a user to login if the user did 
     not exist in the xar_users table.  The code tried to get the uid 
     from the users table and returned if the value was not found.  This 
     circumvented the new functionality in the authldap module that
     tries to create a user in Xaraya if it exists in LDAP but not
     in the Xaraya users table.
    I added code to loop through the authentication modules and set
     the state appropriately.  Also checks if the user exists in the
     xar_users table with a different state, so that an invalid or
     deleted user will not be able to login.

  html/modules/users/xaradminapi.php
    1.31 03/01/23 15:50:13 rcave-rIoA2dxFqdxvvToxOdHx6mP8kLm7lcA4hIvA6WVW+J8@public.gmane.org +6 -5
    Included the field xar_auth_module and set to default authentication
     module 'authsystem' for an admin user create.

  html/modules/users/xaradmin.php
    1.42 03/01/23 15:50:13 rcave-rIoA2dxFqdxvvToxOdHx6mP8kLm7lcA4hIvA6WVW+J8@public.gmane.org +4 -3
    Changed value of 'name' to include actual user name.  Updating to a
     blank name was throwing an error when updating the database because 
     the column xar_name has a unique key and the user 'Anonymous' has 
     a blank name.
    Also included the field xar_auth_module and set to default 
     authentication module 'authsystem' for an admin user create.