Apache Shiro :: Core 2.0.1 API
Packages
Package
Description
This package primarily exists as a root classpath distinction, but it does contain two core classes widely used
by applications,
SecurityUtils and
ShiroException.Components used to support the framework's AOP/interception support classes.
Core interfaces and exceptions concerning Authentication (the act of logging-in).
Support for validating credentials (such as passwords or X509 certificates) during
authentication via the
CredentialsMatcher
interface and its supporting implementations.Support for PAM, or Pluggable Authentication Modules, which is
the capability to authenticate a user against multiple configurable (pluggable) modules (Shiro
calls these
Realms).Core interfaces and exceptions supporting Authorization (access control).
Annotations used to restrict which classes, instances, or methods may be accessed or invoked depending on the
caller's access abilities or authentication state.
Contains AOP implementation support classes specifically used for authorization operations, particularly supporting
AOP Method Interceptors and JSR-175 metadata Annotations.
Support and default implementations for Shiro's
Permission
interface.Executor, ExecutorService,
and ScheduledExecutorService implementations for transparent
Subject association with threads in an asynchronous execution environment.Package containing various components useful when building Data Access Objects (DAOs), including a generic
Data Access Exception hierarchy.
Concepts used to represent Shiro's aggregate state in an application.
Concepts used to represent Shiro's aggregate state in an application.
Enables accessing objects located in JNDI that might be useful when configuring a Shiro-enabled application.
Support for accessing LDAP data sources.
Provides the master
SecurityManager interface and a default implementation
hierarchy for managing all aspects of Shiro's functionality in an application.Components and sub-packages used in supporting the core
Realm interface.Realms that acquire security data from a Microsoft Active Directory.
Realms that acquire security data from an RDBMS (Relational Database Management System) using the
JDBC API.
Support for acquiring Realms from JNDI, particularly useful for configuring Shiro in JEE or EJB environments.
Realms that acquire security data from an LDAP (Lightweight Directory Access Protocol) server
utilizing LDAP/Naming APIs.
Realms that acquire security data from text-based data sources such as
Files or
text streams.Components related to managing sessions, the time-based data contexts in which a Subject
interacts with an application.
SessionManager components supporting enterprise session management.EIS (Enterprise Information System)-tier components that can perform CRUD operations for sessions
using any EIS API.
Components supporting the
Subject interface, the most important concept in
Shiro's API.Concrete support implementations of most of the
org.apache.shiro.subject interfaces.Your run-of-the-mill 'util' package for components and logic widely used across the framework that can't
find their home into a proper OO hierarchy (or, most likely for things used across many hierarchies).