...
As with all interceptors, the exact input state of the context tree is profile-dependent, but generally speaking you will find some important child contexts in the following arrangement:. If you see an error, your browser settings are blocking the macro render. Note that the links no longer work properly on Cloud Confluence, but if you right-click the boxes, you can open the javadoc link in a new tab.
| Digraph |
|---|
node [shape=record] Profile [label="ProfileRequestContext", URL="httpshttp://shibboleth.net/cgi-bin/java-opensaml.cgi/org/opensaml/profile/context/ProfileRequestContext"] RelyingParty [label="RelyingPartyContext", URL="httpshttp://shibboleth.net/cgi-bin/java-identity-provider.cgi/net/shibboleth/idp/profile/context/RelyingPartyContext"] Attribute [label="AttributeContext", URL="httpshttp://shibboleth.net/cgi-bin/java-identity-provider.cgi/net/shibboleth/idp/attribute/context/AttributeContext"] Session [label="SessionContext", URL="httpshttp://shibboleth.net/cgi-bin/java-identity-provider.cgi/net/shibboleth/idp/session/context/SessionContext"] Authentication [label="AuthenticationContext", URL="httpshttp://shibboleth.net/cgi-bin/java-identity-provider.cgi/net/shibboleth/idp/authn/context/AuthenticationContext"] Subject [label="SubjectContext", URL="httpshttp://shibboleth.net/cgi-bin/java-identity-provider.cgi/net/shibboleth/idp/authn/context/SubjectContext"] Profile -> RelyingParty Profile -> Session Profile -> Authentication Profile -> Subject RelyingParty -> Attribute |
...