Home >> All >> org >> acegisecurity >> [ userdetails Javadoc ]

•

org.acegisecurity.userdetails.jdbc.* (1)

•

org.acegisecurity.userdetails.memory.* (5)

• org.acegisecurity.userdetails: Javadoc index of package org.acegisecurity.userdetails.


Package Samples:

• org.acegisecurity.userdetails.memory
• org.acegisecurity.userdetails.jdbc

Classes:

• JdbcDaoImpl: Retrieves user details (username, password, enabled flag, and authorities) from a JDBC location. A default database structure is assumed, (see DEF_USERS_BY_USERNAME_QUERY 55 and DEF_AUTHORITIES_BY_USERNAME_QUERY 55 , which most users of this class will need to override, if using an existing scheme. This may be done by setting the default query strings used. If this does not provide enough flexibility, another strategy would be to subclass this class and override the org.springframework.jdbc.object.MappingSqlQuery instances used, via the initMappingSqlQueries() 55 extension point. In order to minimise ...
• UserMapEditor: Property editor to assist with the setup of a UserMap . The format of entries should be: username=password,grantedAuthority[,grantedAuthority][,enabled|disabled] The password must always be the first entry after the equals. The enabled or disabled keyword can appear anywhere (apart from the first entry reserved for the password). If neither enabled or disabled appear, the default is enabled . At least one granted authority must be listed. The username represents the key and duplicates are handled the same was as duplicates would be in Java Properties files. If the above requirements are not met, ...
• UserDetails: Provides core user information. Implementations are not used directly by Acegi Security for security purposes. They simply store user information which is later encapsulated into org.acegisecurity.Authentication objects. This allows non-security related user information (such as email addresses, telephone numbers etc) to be stored in a convenient location. Concrete implementations must take particular care to ensure the non-null contract detailed for each method is enforced. See org.acegisecurity.providers.dao.User for a reference implementation (which you might like to extend).
• User: Models core user information retieved by an UserDetailsService . Implemented with value object semantics (immutable after construction, like a String ). Developers may use this class directly, subclass it, or write their own UserDetails implementation from scratch.
• UserDetailsService: Defines an interface for implementations that wish to provide data access services to the org.acegisecurity.providers.dao.DaoAuthenticationProvider . The interface requires only one read-only method, which simplifies support of new data access strategies.
• UsernameNotFoundException: Thrown if an UserDetailsService implementation cannot locate a User by its username.
• UserMap: Used by InMemoryDaoImpl to store a list of users and their corresponding granted authorities.
• UserAttribute: Used by InMemoryDaoImpl to temporarily store the attributes associated with a user.
• UserAttributeEditor: Property editor that creates a UserAttribute from a comma separated list of values.
• InMemoryDaoImpl: Retrieves user details from an in-memory list created by the bean context.

Home | Contact Us | Privacy Policy | Terms of Service