Best Web Hosting - JBoss 3.0 Guide - Best Hosting Services

S E C U R I T Y

optional   The LoginModule is not required to succeed. If it succeeds

or fails, authentication still continues to proceed down the

LoginModule list.

The code attribute gives the fully qualifed class name of the

javax.security.auth.spi.LoginModule interface implementation for the login module.

A policy/application policy/authentication/login module/module option

element specifies a login module option name/value pair.

The name attribute specifies the name of the login module option.

The element value is the option value string representation.

The following listing shows a sample configuration file.

Listing 8 1, A sample login configuration for the XMLLoginConfigservice.

             flag = "required">

             sample.users

             sample.roles

JAAS LoginModules Bundled With JBoss

JBoss comes with a number of JAAS LoginModule implementations that support commonly

used security stores such as JDBC databases and LDAP servers. The most commonly used

login modules are presented in the following subsections.

o r g . j b o s s . s e c u r i t y . a u t h . s p i . U s e r s R o l e s L o g i n M o d u l e

The UsersRolesLoginModule is another simple login module that supports multiple users

and user roles, and is based on two Java Properties formatted text files. The username to

password mapping file is called "users.properties" and the username to roles mapping file is

called "roles.properties". The properties files are loaded during initialization using the

initialize method thread context class loader. This means that these files can be placed into

the J2EE deployment jar, the JBoss configuration directory, or any directory on the JBoss

server or system classpath. The primary purpose of this login module is to easily test the

security settings of multiple users and roles using properties files deployed with the

application.

footer