public abstract class AbstractPasswordBasedSecurityRealm extends SecurityRealm implements org.acegisecurity.userdetails.UserDetailsService
SecurityRealm
for username/password based authentication.
This is a convenience base class if all you are trying to do is to check the given username
and password with the information stored in somewhere else, and you don't want to do anything
with Acegi.
This SecurityRealm
uses the standard login form (and a few other optional mechanisms like BASIC auth)
to gather the username/password information. Subtypes are responsible for authenticating this information.
SecurityRealm.SecurityComponents
ExtensionPoint.LegacyInstancesAreScopedToHudson
AUTHENTICATED_AUTHORITY, LIST, NO_AUTHENTICATION
Constructor and Description |
---|
AbstractPasswordBasedSecurityRealm() |
Modifier and Type | Method and Description |
---|---|
protected abstract org.acegisecurity.userdetails.UserDetails |
authenticate(String username,
String password)
Authenticate a login attempt.
|
CliAuthenticator |
createCliAuthenticator(CLICommand command)
Creates a
CliAuthenticator object that authenticates an invocation of a CLI command. |
SecurityRealm.SecurityComponents |
createSecurityComponents()
Creates fully-configured
AuthenticationManager that performs authentication
against the user realm. |
abstract GroupDetails |
loadGroupByGroupname(String groupname)
Retrieves information about a group by its name.
|
abstract org.acegisecurity.userdetails.UserDetails |
loadUserByUsername(String username)
Retrieves information about an user by its name.
|
all, allowsSignup, canLogOut, commenceSignup, createFilter, doCaptcha, doLogout, findBean, getAuthenticationGatewayUrl, getCaptchaSupport, getCaptchaSupportDescriptors, getDescriptor, getGroupIdStrategy, getLoginUrl, getPostLogOutUrl, getSecurityComponents, getUserIdStrategy, loadGroupByGroupname, setCaptchaSupport, validateCaptcha
public SecurityRealm.SecurityComponents createSecurityComponents()
SecurityRealm
AuthenticationManager
that performs authentication
against the user realm. The implementation hides how such authentication manager
is configured.
AuthenticationManager
instantiation often depends on the user-specified parameters
(for example, if the authentication is based on LDAP, the user needs to specify
the host name of the LDAP server.) Such configuration is expected to be
presented to the user via config.jelly and then
captured as instance variables inside the SecurityRealm
implementation.
Your SecurityRealm
may also wants to alter Filter
set up by
overriding SecurityRealm.createFilter(FilterConfig)
.
createSecurityComponents
in class SecurityRealm
public CliAuthenticator createCliAuthenticator(CLICommand command)
SecurityRealm
CliAuthenticator
object that authenticates an invocation of a CLI command.
See CliAuthenticator
for more details.createCliAuthenticator
in class SecurityRealm
command
- The command about to be executed.Jenkins.ANONYMOUS
.)protected abstract org.acegisecurity.userdetails.UserDetails authenticate(String username, String password) throws org.acegisecurity.AuthenticationException
AbstractPasswordBasedSecurityRealm
.
If the user name and the password pair matches, retrieve the information about this user and
return it as a UserDetails
object. User
is a convenient
implementation to use, but if your backend offers additional data, you may want to use your own subtype
so that the rest of Hudson can use those additional information (such as e-mail address --- see
MailAddressResolver.)
Properties like UserDetails.getPassword()
make no sense, so just return an empty value from it.
The only information that you need to pay real attention is UserDetails.getAuthorities()
, which
is a list of roles/groups that the user is in. At minimum, this must contain SecurityRealm.AUTHENTICATED_AUTHORITY
(which indicates that this user is authenticated and not anonymous), but if your backend supports a notion
of groups, you should make sure that the authorities contain one entry per one group. This enables
users to control authorization based on groups.
If the user name and the password pair doesn't match, throw AuthenticationException
to reject the login
attempt.
org.acegisecurity.AuthenticationException
public abstract org.acegisecurity.userdetails.UserDetails loadUserByUsername(String username) throws org.acegisecurity.userdetails.UsernameNotFoundException, org.springframework.dao.DataAccessException
This method is used, for example, to validate if the given token is a valid user name when the user is configuring an ACL.
This is an optional method that improves the user experience. If your backend doesn't support
a query like this, just always throw UsernameNotFoundException
.
loadUserByUsername
in interface org.acegisecurity.userdetails.UserDetailsService
loadUserByUsername
in class SecurityRealm
org.acegisecurity.userdetails.UsernameNotFoundException
org.springframework.dao.DataAccessException
public abstract GroupDetails loadGroupByGroupname(String groupname) throws org.acegisecurity.userdetails.UsernameNotFoundException, org.springframework.dao.DataAccessException
loadUserByUsername(String)
.loadGroupByGroupname
in class SecurityRealm
org.acegisecurity.userdetails.UsernameNotFoundException
org.springframework.dao.DataAccessException
Copyright © 2019. All rights reserved.