The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »


A standard IdP configuration provides you with many "named beans" which are there to simplify configuration and to reduce the burden of remembering the specific class names.   For ease of navigation, this topic divides them into three groups,  Predicates (including ActivationConditions), Functions and other beans.

Predicates

All Predicates beans are implementation of the Predicate interface, that is to say they are given a "thing" and return true or false.

Logic

Activation

The most important use of Predicates is in ActivationConditions, and the majority of the predefined beans are of this type.   They implement  Predicate<ProfileRequestContext>, and will be called with the current Request context (when provided as a activation condition.

Other useful Predicate classes

These are not named beans, but the classes can be useful

  • net.shibboleth.idp.profile.logic.SimpleAttributePredicate
  • org.opensaml.profile.logic.IPRangePredicate
  • net.shibboleth.utilities.java.support.logic.StrategyIndirectedPredicate

See Also

Functions

Context Functions

  • shibboleth.MessageContextLookup.Inbound
  • shibboleth.ContextFunctions.Scripted
  • shibboleth.ContextFunctions.Expression
  • shibboleth.MessageContextLookup.Inbound
  • shibboleth.MessageContextLookup.Outbound
  • shibboleth.MessageLookup.SAMLObject
  • shibboleth.MessageLookup.AuthnRequest

Other Functions

Other Beans

  • shibboleth.Pair
  • shibboleth.CommaDelimStringArray
  • shibboleth.NonFailFastValidator
  • shibboleth.HttpServletRequest
  • shibboleth.HttpServletResponse

Alphabetic listing

  • No labels