Authentication and loginModules

after the user transmits its credentials through the authentication scheme, jGuard should authenticate the user with them.

to authenticate the user, jGuard use its credentials against some security challenges: LoginModules. loginModules are stackable: you can configure multiple loginModules (in the jGuardConfiguration.xml file),which will help you to authenticate a user or not.

each loginModule has got a flag which can be 'REQUIRED','OPTIONAL','REQUISITE' ou 'SUFFICIENT' (JAAS documentation from SUN):

• REQUIRED

The LoginModule is required to succeed. If it succeeds or fails, authentication still continues to proceed down the LoginModule list.

• REQUISITE

The LoginModule is required to succeed. If it succeeds, authentication continues down the LoginModule list.If it fails, control immediately returns to the application (authentication does not proceed down the LoginModule list).

• SUFFICIENT

The LoginModule is not required to succeed. If it does succeed, control immediately returns to the application (authentication does not proceed down the LoginModule list).If it fails, authentication continues down the LoginModule list.

• OPTIONAL

The LoginModule is not required to succeed. If it succeeds or fails, authentication still continues to proceed down the LoginModule list.

loginModules provided

here are the list of the loginModules provided:

• XmlLoginModule
• JdbcLoginModule
• JNDILoginModule
• CRLLoginModule
• OCSPLoginModule

implements your own loginModule

you can add your own loginModule on the authentication loginModules list.

to do it, you have to implements the javax.security.auth.spi.LoginModule interface.