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

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

On Fri, 29 Oct 2004, Matthew White wrote:
> Ok, so... I've got things smoothly working with reqadm so far...  we've
> got users authentication with apache/LDAP and pulling userifo out of a
> home-brew userinfo server.  here's the issue: when a users phone number
> is updated in our LDAP database (where the userinfo server is getting
> its information) it's not reflected in a user's "profile" within reqadm.
> Is there a way to change this behavior?

The way REQADM was designed, it looks for updates from userinfo via
nightly cron job which pulls the userinfo data and merges it with
REQADM's own database.  It looks for the modification date (one of 
the fields in the userinfo data) and ignores any record which was
modified less recently than REQADM's own profile.  So you need to
get that date field updated as well.

I'm working now on the migration of REQADM to SQL, and when that is
ready for release, the behavior will be for REQADM to just read the
profile table which will be much easier for random site processes
to update.  This will do away with all the userinfo stuff you see in
REQADM today, which is a legacy bridge to the old environment REQADM
was originally custom-built for.

-- 
Steve Willoughby     | "It is our choices... that show what we truly 
<st...@al...>  | are, far more than our abilities."
                     |     --Albus Dumbledore, in Harry Potter and the 
                     |            Chamber of Secrets, by J. K. Rowling