Login Module ${status.index+1}
Login Domain Name:
<%-- Can't change the login domain name after deployment because it's how we know which GBean is which --%>
The login domain for this login module, which must be unique among all modules in the security realm.
This can be used to distinguish principals from two otherwise identical login modules (for example,
from two LDAP login modules pointing to two different LDAP servers)
Login Module Class:
The fully-qualified class name for the login module.
Control Flag:
selected>Optional
selected>Required
selected>Requisite
selected>Sufficient
The control flag for the login module, which controls what happens to the overall login processing if this
login module succeeds or fails. For more information see
javax.security.auth.login.Configuration .
Server-Side:
selected>Server Side
selected>Client Side
Server-side login modules are executed within the application server (this is normally correct). Client-side
login modules are executed in the client's environment, for example, in order to use single sign-on features
of the client OS.
Support Advanced Mapping:
selected>Yes
selected>No
Normally Geronimo can't distinguish between two different principals that have the same name
and same principal class but were produced by two different login modules. If this option is
enabled, Geronimo will "wrap" principals to track which login module and realm each
principal came from. This lets you use the "realm-principal" and "login-domain-principal"
elements in your security mapping in Geronimo deployment plans.
Configuration Options:
Any configuration options necessary for the login module, in the standard Java properties format (one
per line, name=value )