Caching of attributes retrieved by attribute query in the SP

Jonas Dehlin jonas.dehlin.crap at gmail.com
Fri Dec 14 08:23:27 EST 2012


Thank you Peter for confirming my suspicions. I will take this into
consideration when moving forward.

Kind regards,
Jonas


On Fri, Dec 14, 2012 at 1:48 PM, Peter Schober
<peter.schober at univie.ac.at>wrote:

> * Peter Schober <peter.schober at univie.ac.at> [2012-12-14 13:42]:
> > * Jonas Dehlin <jonas.dehlin.crap at gmail.com> [2012-12-14 13:29]:
> > > Essentially, what I need to do is make a lookup for the attribute
> > > value for each incoming request since I always need the latest
> > > value.
> >
> > I don't think the software allows to do this today.
>
> More to the point: Once the session is gone either active protection
> of the SP kicks in (if used) or you end up at the resource unauthenticated.
>
> Once a new session is initiated the standard SSO flow begins and a new
> session gets established (whether that involves attribute queries or
> not is immaterial here), replacing whatever was there before wholesale.
>
> So I don't think the existing architecture can do what you want.
> -peter
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20121214/040183d7/attachment-0001.html 


More information about the users mailing list