This is an XML Schema Definition for login module configuration to
use for particular security module. Login module configuration is
specified by the level element as login-config with namespace
specified as xmlns =
"http://geronimo.apache.org/xml/ns/loginconfig-2.0". The default
location for this document is somewhere vaguely related to
http://geronimo.apache.org/schemas-1.2/geronimo-login-config-2.0.xsd
The definition of the XML format for storing login-config should
look like this:
some-name
org.apache.geronimo.LoginModuleClass
]]>
Import Geronimo Services deployment plans, the imported plan
includes complex types like moduleType, environmentType,
dependenciesType, etc. required by this plan schema.
The root element for Geronimo login module configuration. This
configuration can either refer to existing login module or
define a new login configuration. Note that the sub-elements of
this element should be as in the given order in sequence.
Defines the list of login modules for a login configuration
represented by a GenericSecurityRealm
The login-module-ref element defines a reference to
existing login module configured in some other
GBean.
The login-module element defines a new login module
configuration. It should provide the complete
information to GBean module being referred.
The control-flag attribute specifies the JAAS control flag
used for this a login module configuration. It can be
REQUIRED, REQUISITE, SUFFICIENT, or OPTIONAL as defined by
JAAS API's.
This boolean attribute specifies if the principals are
wrapped in this login module.
Include attributes defined in abstract-login-moduleType
above.
The pattern element defines a components of the
abstract name of GBean referred. It includes
information like groupId, artifactId, version,
module, type, and name of the GBean module.
REQUIRED: Defines the requirement of this login module
configuration for authentication. In any case, control
will proceed to next login module.
REQUISITE: Defines the requirement of this login module
configuration for authentication. On failure, control
will return to application else proceed to next login
module.
SUFFICIENT: Defines the non-requirement of this login
module configuration for authentication. On success,
control will return to application else proceed to next
login module.
OPTIONAL: Defines the requirement of this login module
configuration for authentication. In any case, control
will return to application.
Include attributes defined in abstract-login-moduleType
above.
This element defines a unique domain name to
each configuration of login module. This allows
configuration of same login module multiple
times with different domain name.
This provides the name of class which provides
implementation of this LoginModule. This name
should be fully qualified java class name. Also
this class should have implemented
javax.security.auth.spi.LoginModule interface.
The name value pair for options (properties)
required by this login module.
The name attribute specifies the name of option. The
value is specified by element value.