This shouldn't cause any problems, but I'll mention it anyway, just in case. :) FYI, I made a couple of minor updates to LCRC's copy of the Accounts webpage which can change users' data in userbase: 1) The LCRC version of the Personal Account page never had a field for changing ones "unix" password, like the MCS version. I added a field for this now, although it is only available for users with an "LCRC" account_type; other users are directed to MCS's Accounts website for changing their "unix" password. The background for this is since LCRC's cluster (fusion) uses SSH keys for logging in, the "unix" password is only used for logging into the Accounts website. In the bad old days of Jazz, the LCRC Accounts website was getting passwords out of NIS (which were initially set to the crypted passwords from userbase), so if you wanted to change your password for accessing the Accounts site, you had to run yppasswd (at which point the crypt in userbase and the crypt in NIS would be out of sync). Since on fusion we're now using LDAP which has no password crypts, the LCRC Accounts website uses the crypts stored in userbase directly. However, non-MCS users had no way to change this password, since they couldn't log into MCS's version of the Accounts page. Now they do. Since it looks like the MCS Accounts page may store user passwords in places (eg, kerberos) in addition to userbase, the LCRC Accounts page redirects MCS users to the MCS Accounts page, so that their password doesn't get out of sync. 2) When an Argonne user requests an account via the LCRC Account Request page, the LCRC Account pages will now automatically set the argonne_username field in userbase for that user to the user's Argonne username. This field is displayed in the user's LCRC Personal Account page, but it isn't editable at the moment (as it is in MCS's version of that page). John