Examples of JDBCRealm

com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm
Realm for supporting JDBC authentication.
The JDBC realm needs the following properties in its configuration:
- jaas-context : JAAS context name used to access LoginModule for authentication (for example JDBCRealm).
- datasource-jndi : jndi name of datasource
- db-user : user name to access the datasource
- db-password : password to access the datasource
- digest: digest mechanism
- charset: charset encoding
- user-table: table containing user name and password
- group-table: table containing user name and group name
- user-name-column: column corresponding to user name in user-table and group-table
- password-column : column corresponding to password in user-table
- group-name-column : column corresponding to group in group-table
@see com.sun.enterprise.security.auth.login.SolarisLoginModule
com.sun.enterprise.security.ee.auth.realm.jdbc.JDBCRealm
Realm for supporting JDBC authentication.
The JDBC realm needs the following properties in its configuration:
- jaas-context : JAAS context name used to access LoginModule for authentication (for example JDBCRealm).
- datasource-jndi : jndi name of datasource
- db-user : user name to access the datasource
- db-password : password to access the datasource
- digest: digest mechanism
- charset: charset encoding
- user-table: table containing user name and password
- group-table: table containing user name and group name
- user-name-column: column corresponding to user name in user-table and group-table
- password-column : column corresponding to password in user-table
- group-name-column : column corresponding to group in group-table
@see com.sun.enterprise.security.auth.login.SolarisLoginModule
org.apache.catalina.realm.JDBCRealm
Implmentation of Realm that works with any JDBC supported database. See the JDBCRealm.howto for more details on how to set up the database and for configuration options.
TODO - Support connection pooling (including message format objects) so that authenticate(), getPassword() and authenticate() do not have to be synchronized and would fix the ugly connection logic.
@author Craig R. McClanahan @author Carson McDonald @author Ignacio Ortega @version $Revision: 543691 $ $Date: 2007-06-02 03:37:08 +0200 (Sat, 02 Jun 2007) $
org.apache.shiro.realm.jdbc.JdbcRealm
Realm that allows authentication and authorization via JDBC calls. The default queries suggest a potential schema for retrieving the user's password for authentication, and querying for a user's roles and permissions. The default queries can be overridden by setting the query properties of the realm.
If the default implementation of authentication and authorization cannot handle your schema, this class can be subclassed and the appropriate methods overridden. (usually {@link #doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken)}, {@link #getRoleNamesForUser(java.sql.Connection,String)}, and/or {@link #getPermissions(java.sql.Connection,String,java.util.Collection)}
This realm supports caching by extending from {@link org.apache.shiro.realm.AuthorizingRealm}. @since 0.2

Examples of org.apache.shiro.realm.jdbc.JdbcRealm

    private JdbcRealm jdbcRealm;


    private PasswordDigester passwordDigester;


    public JDBCUserStore() {
        jdbcRealm = new JdbcRealm();
    }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.