By the way, a similar thread on the ezproxy list brought up this list:
Which is apparently about ILLiad best practices. I've just subscribed and
started reading through the archives.
University of Illinois
On Thu, Jul 11, 2013 at 3:53 PM, Jimmy Ghaphery <[log in to unmask]> wrote:
> yeh for us we did go with the documentation as best we could and use an
> filter. The final straw for us as a hosted site was that OCLC said they
> could not support this method and steered us to the EzProxy auth method.
> On Thu, Jul 11, 2013 at 4:13 PM, Jon Gorman <[log in to unmask]
> > > I am also following this conversation, I am wondering if you consult
> > following about RemoteAuth Authentication,
> > > but still failed?
> > >
> > >
> > >
> > > Ling
> > > UIC Library
> > Don't know about Jimmy, but the flow on that page is one of the issues we
> > have. We can't trigger the system to have that login behavior. From
> what I
> > can tell of the logs, it decides the page to redirect to in a session
> > before it ever checks the user status or the remote user header. I don't
> > know how, given that, that the flow could really happen that way. (I
> > be missing something).
> > As far as I can tell the other settings are what they should be, after
> > if they weren't I can't imagine that it would work most of the time, just
> > not on the initial logon.
> > We did have an issue with a session heartbeat type of thing that had a
> > similar behavior (the headers would just drop off, somehow associated
> > the heartbeat process). Thankfully we were able to disable that in the
> > authentication software.
> > Does anyone using RemoteAuth actually see that flow (get challenged to
> > either register or update your info after first successful login?) If
> > do, what are you using as a link into the system?
> > Jon Gorman
> > University of Illinois
> Jimmy Ghaphery
> Head, Digital Technologies
> VCU Libraries