| java.lang.Object
 org.mmbase.security.Configurable
org.mmbase.security.Authentication
All known Subclasses: org.mmbase.security.implementation.context.ContextAuthentication, org.mmbase.security.NoAuthentication, org.mmbase.security.implementation.basic.AuthenticationHandler, org.mmbase.security.classsecurity.ClassAuthenticationWrapper,
| Authentication | | abstract public class Authentication extends Configurable implements AuthenticationData(Code) | | This class is a abstract implementation of the Authentication.
To make your own implementation of authentication, you have to extend this class.
author:
Eduard Witteveen
author:
Michiel Meeuwissen (javadocs)
version:
$Id: Authentication.java,v 1.41 2008/01/21 15:25:28 michiel Exp $ |
| PARAMETERS_ANONYMOUS | | final protected static Parameter[] PARAMETERS_ANONYMOUS(Code) | | |
| PARAMETERS_NAME_PASSWORD | | final protected static Parameter[] PARAMETERS_NAME_PASSWORD(Code) | | |
| getDefaultMethod | | public int getDefaultMethod(String protocol)(Code) | |
since:
MMBase-1.8 |
| getKey | | public long getKey()(Code) | | Some unique key associated with this security configuration. It can be explicitely set with
the 'key' entry in security.xml. It falls back to the current time in milliseconds at the time of
initialization of authentication.
The advantage of explicitely configuring it, is that serialized user-contextes remain valid
after a restart of MMBase, and users need not to log in again then.
since:
MMBase-1.8 |
| getMethod | | final public int getMethod(String m)(Code) | |
since:
MMBase-1.8 |
| getMethod | | final public static String getMethod(int m)(Code) | |
since:
MMBase-1.9 |
| getTypes | | public String[] getTypes(int method)(Code) | |
since:
MMBase-1.8 |
| login | | abstract public UserContext login(String application, Map<String, Object> loginInfo, Object[] parameters) throws SecurityException(Code) | | This method will verify the login, and give a UserContext back if the login procedure was successful.
Parameters:
application - A String that further specifies the login method (one implementation could handle more then one methods)A typical value might be 'username/password'.Possible values are returned by Authentication.getTypes.This is also called 'authentication', or '(authentication) type' inseveral contextes.
Parameters:
loginInfo - A Map containing the credentials or other objects which might be used to obtain them (e.g. request/response objects).It might also be 'null', in which case your implementation normally should return the 'anonymous' user (or null, ifno such user can be defined). This Map can (or must) be supplied byAuthentication.createParameters (using the setter-methods and the Parameters.toMap method of the resulting Parameters object).
Parameters:
parameters - A list of optional parameters, may also (and will often) be null. null if no valid credentials were supplied, a (perhaps new) UserContext if login succeeded.
exception:
SecurityException - When something strange happened, or authentication was unsucessfull. |
|
|