Known Indirect Subclasses
Represents the token for an authentication request or for an authenticated principal once the request has been
processed by the
Once the request has been authenticated, the Authentication will usually be stored in a thread-local
SecurityContext managed by the
SecurityContextHolder by the authentication mechanism which is
being used. An explicit authentication can be achieved, without using one of Spring Security's authentication
mechanisms, by creating an Authentication instance and using the code:
SecurityContextHolder.getContext().setAuthentication(anAuthentication);Note that unless the Authentication has the authenticated property set to true, it will still be authenticated by any security interceptor (for method or web invocations) which encounters it.
In most cases, the framework transparently takes care of managing the security context and authentication objects for you.
Set by an
The credentials that prove the principal is correct.
Stores additional details about the authentication request.
The identity of the principal being authenticated.
Used to indicate to
|From interface java.security.Principal|
Set by an
AuthenticationManager to indicate the authorities that the principal has been
granted. Note that classes should not rely on this value as being valid unless it has been set by a trusted
Implementations should ensure that modifications to the returned collection array do not affect the state of the Authentication object, or use an unmodifiable instance.
The credentials that prove the principal is correct. This is usually a password, but could be anything
relevant to the
AuthenticationManager. Callers are expected to populate the credentials.
Stores additional details about the authentication request. These might be an IP address, certificate serial number etc.
nullif not used
The identity of the principal being authenticated. In the case of an authentication request with username and password, this would be the username. Callers are expected to populate the principal for an authentication request.
The AuthenticationManager implementation will often return an Authentication containing
richer information as the principal for use by the application. Many of the authentication providers will
UserDetails object as the principal.
Principalbeing authenticated or the authenticated principal after authentication.
Used to indicate to
AbstractSecurityInterceptor whether it should present the
authentication token to the
AuthenticationManager. Typically an
(or, more often, one of its
AuthenticationProviders) will return an immutable authentication token
after successful authentication, in which case that token can safely return
true to this method.
true will improve performance, as calling the
every request will no longer be necessary.
For security reasons, implementations of this interface should be very careful about returning
true from this method unless they are either immutable, or have some way of ensuring the properties
have not been changed since original creation.
AbstractSecurityInterceptordoes not need to present the token to the
AuthenticationManageragain for re-authentication.
isAuthenticated() for a full description.
Implementations should always allow this method to be called with a
as this is used by various classes to specify the authentication token should not be trusted.
If an implementation wishes to reject an invocation with a
true parameter (which would indicate
the authentication token is trusted - a potential security risk) the implementation should throw an