Re: [REQADM-Users-L] caching userinfo - disable-able?. I

[Steve W. <st...@ic...>]

On Tue, 2 Nov 2004, Matthew White wrote:
> thought I had it... now I don't.

Pretty much.  I'll simplify slightly.

usertable, cdis, password file/NIS, etc. all get loaded into the
REQADM database when you install REQADM and periodically (reqadm-nightly)
thereafter.  This is your active customer base.

REQADM gets a request from someone who isn't in the REQADM database.

What happens next depends on how we got the person's ticket.  If we already
have an RUID, REQADM will just query userinfo to get the info for the
user's account.

If we only have an email address, it will try LDAP to get a RUID from the
mail address and then ask userinfo.

If we can't get an RUID, REQADM will invent one in the "temporary RUID"
number range, fill in a few of the profile fields and proceed.

> SO, if I want to change someone's information, I need to add that person
> to the cdis file and make sure their modification date is later than
> when the user was fist stuffed into the dbase.  Then after the nightly
> cron script is run, that user's info will be update.

Right, except that the date should be later than the last update to the
user's REQADM profile (either from a previous update via cron or the
person editing their profile from within REQADM).

-- 
Steve Willoughby          | "The purpose of IT is to seamlessly and trans-
Intel DPG Eng. Computing  | parently provide the other nine-tenths of the
Application Development   | iceberg for people who need to work with chunks
<st...@ic...>  | of floating ice."           --Strata R. Chalup