...
Form-based authentication lets developers customize the authentication user interface. While the J2EE specifications provide a standard way to specify the login page URL access requirements, there still is container-specific configuration to specify how to read usernames and passwords from a security datastore. This is one reason that the platform uses Acegi Security. The Acegi Security class that processes form posts is AuthenticationProcessingFilter
.
Login Page
Panel |
---|
bgColor | #FFFFFF |
---|
title | Login Page |
---|
|
Image Added |
Panel |
---|
bgColor | #FFFFFF |
---|
title | Blank Login Form |
---|
|
Image Added |
Panel |
---|
bgColor | #FFFFFF |
---|
title | Login Form After Bad Credentials Submitted |
---|
|
Image Added |
Panel |
---|
bgColor | #FFFFFF |
---|
title | Login Form After Generic Security Error |
---|
|
Image Added |
Panel |
---|
bgColor | #FFFFFF |
---|
title | Login Form While Logged In |
---|
|
Image Added |
Panel |
---|
bgColor | #FFFFFF |
---|
title | Login Form After Session Re-Use Detected |
---|
|
Image Added |
Image Added
Logout Page
Basic Authentication
Basic authentication is part of the HTTP specification. It is simple but relatively inflexible. Acegi Security implements Basic authentication using BasicProcessingFilter
and BasicProcessingFilterEntryPoint
.
...