Transient data associated with the current client for the security check
Aggregates authorization responses from multiple security checks.
Aggregates introspection responses from multiple security checks.
Persistent/deployment data associated with the current client
Represents server-side state of a security check.
Security checks are kept in a distributed cache, and are stateful, so it's the responsibility of the implementor to handle the persistent state.
Represents the configuration of a security check.
Is created during deployment via
The subclasses are responsible for reading the configuration data from the Properties object and validating it.
Field annotation that defines a reference to a security check, creating a dependency between the checks.
The annotation is applied to a field definition within a security-check class.
© Copyright IBM Corp. 2006, 2015. All Rights Reserved.