Package org.owasp.esapi.reference

This package contains reference implementations of the ESAPI interfaces.

See:
Description

Class Summary

AbstractAccessReferenceMap<K>	Abstract Implementation of the AccessReferenceMap that is backed by ConcurrentHashMaps to provide a thread-safe implementation of the AccessReferenceMap.
AbstractAuthenticator	A partial implementation of the Authenticator interface.
DefaultAccessController
DefaultEncoder	Reference implementation of the Encoder interface.
DefaultExecutor	Reference implementation of the Executor interface.
DefaultHTTPUtilities	Reference implementation of the HTTPUtilities interface.
DefaultIntrusionDetector	Reference implementation of the IntrusionDetector interface.
DefaultRandomizer	Reference implementation of the Randomizer interface.
DefaultSecurityConfiguration	The reference SecurityConfiguration manages all the settings used by the ESAPI in a single place.
DefaultUser	Reference implementation of the User interface.
DefaultValidator	Reference implementation of the Validator interface.
FileBasedAuthenticator	Reference implementation of the Authenticator interface.
IntegerAccessReferenceMap	Reference implementation of the AccessReferenceMap interface.
JavaLogFactory	Reference implementation of the LogFactory and Logger interfaces.
JavaLogFactory.JavaLoggerLevel	A custom logging level defined between Level.SEVERE and Level.WARNING in logger.
Log4JLogFactory	Reference implementation of the LogFactory interface.
Log4JLogger	Reference implementation of the Logger interface.
Log4JLoggerFactory	Implementation of the LoggerFactory interface.
RandomAccessReferenceMap	Reference implementation of the AccessReferenceMap interface.

Package org.owasp.esapi.reference Description

This package contains reference implementations of the ESAPI interfaces. These are intended to serve as examples of how your enterprise might implement these functions. The reference implementations are high quality and pass all of the ESAPI test cases. Many of the reference implementations are likely to be useful in your enterprise without change (Validator, Encoder, Encryptor, etc...). Implementing other classes (Authenticator, User, AccessController, Logger, etc...) will likely need to be customized for your enterprise, to integrate with your backend systems and policies.