...
Trust Engines must implement the org.opensaml.xml.security.trust.TrustEngine
interface. Particular implementations, some of which are described in the next section, may require some information at construction time, but once you have constructed an instance, the usage will be as described here. A given trust engine implementation will be parameterized with the type of token it processes, such as a Credential
or Signature
.
The main trust engine interface method is validate(TokenType token, CriteriaSet trustBasisCriteria)
. A given trust engine implementation will be parameterized with the type of token it processes, such as a Credential
or Signature
, which has a boolean
return type. If true
, the token was valid and trusted; if false
, it was either invalid or could not be established as trusted. An exception org.opensaml.xml.security.SecurityException
is thrown if there is a problem evaluating the token.
The org.opensaml.xml.security.CriteriaSet
parameter specifies the criteria for validating the token and establishing trust. This criteria set will contain one or more instances of org.opensaml.xml.security.Criteria
. The mandatory and optional types of criteria which can be supplied in the set are specific to a particular trust engine implementation. In turn, these are therefore often typically directly related to (and often in fact wholly defined by) the requirements of an underlying trusted information resolver, such as org.opensaml.xml.security.credential.CredentialResolver
and org.opensaml.xml.security.x509.PKIXValidationInformationResolver
.
...