AuthenticationContext persistence
Klingenstein, Nate
nklingenstein at calstate.edu
Mon Aug 29 20:21:49 EDT 2016
The authentication context appears to persist across requests(e.g. getActiveResults) but some of the information available on the object seems really request-specific(e.g. isPassive). Is there a consistent rule that determines what is in and what is out and is there reasoning behind that that I risk breaking?
https://build.shibboleth.net/nexus/service/local/repositories/site/content/java-identity-provider/3.2.1/apidocs/net/shibboleth/idp/authn/context/AuthenticationContext.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160830/4ceb1846/attachment.html>
More information about the dev
mailing list