org.keel.apps.register.models
Class Login
java.lang.Object
org.keel.services.model.StandardModel
org.keel.services.model.StandardLogEnabledModel
org.keel.apps.register.models.LoginBase
org.keel.apps.register.models.Login
- All Implemented Interfaces:
- Configurable, LogEnabled, Model
- public class Login
- extends LoginBase
The encryption that is applied to both passwords stored in the persistent store and stored in the cookie on the user side is fully configurable. In the configuration for this model, a section:
<password> <seq>base64np.encrypt> </password>
Will apply the base64np Encryptor service, using the "encrypt" method. You can also use the "hash" method (for one-way hashing) by specifying "hash" instead of "encrypt". Multiple "seq" tags are allowed, and will be applied in order, then in reverse order when de-crypting. To specify the sequence for cookies, use "cookie" instead of "password" as the top-level element. Note: Don't use "hash" for cookies, as they need to be de-cryptable, not just hashable. Also: Do this exact same sequence of configuration for the "verify- login" model as well for automatic logins via cookie.
- Version:
- $Revision: 1.13 $ $Date: 2004/05/10 20:09:35 $
- Author:
- Mike Nash, Shash Chatterjee Created on Jun 8, 2003
| Fields inherited from interface org.keel.services.model.Model |
ROLE |
| Constructor Summary |
Login()
|
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Login
public Login()
execute
public ModelResponse execute(ModelRequest req)
throws ModelException
-
- Throws:
ModelException
Please see keelframework.org for information about new Keel releases.