| org.apache.lenya.ac.file.FileUser
 org.apache.lenya.ac.ldap.LDAPUser
| LDAPUser | | public class LDAPUser extends FileUser (Code) | | LDAP user.
version:
$Id: LDAPUser.java 580116 2007-09-27 18:02:21Z rfrovarp $ |
| LDAP_ID | | final public static String LDAP_ID(Code) | | LDAP_ID The LDAP id
|
| LDAPUser | | public LDAPUser(ItemManager itemManager, Logger logger)(Code) | | Creates a new LDAPUser object.
Parameters:
itemManager - The item manager.
Parameters:
logger - The logger. |
| LDAPUser | | public LDAPUser(ItemManager itemManager, Logger logger, String id, String email, String _ldapId, Logger _logger) throws ConfigurationException(Code) | | Create an LDAPUser
Parameters:
itemManager - The item manager.
Parameters:
logger - The logger.
Parameters:
id - user id of LDAPUser
Parameters:
email - of LDAPUser
Parameters:
_ldapId - of LDAPUser
Parameters:
_logger - The logger.
throws:
ConfigurationException - if the properties could not be read |
| authenticate | | public boolean authenticate(String password)(Code) | | Authenticate a user against the directory. The principal to be
authenticated is either constructed by use of the configured properties,
or by lookup of this ID in the directory. This principal then attempts to
authenticate against the directory with the provided password.
See Also: org.apache.lenya.ac.User.authenticate(java.lang.String) |
| canChangePassword | | public boolean canChangePassword()(Code) | | The LDAPUser doesn't change any passwords as they are handled by LDAP
always returns false |
| configure | | public void configure(Configuration config) throws ConfigurationException(Code) | | Create a new LDAPUser from a configuration
Parameters:
config - the Configuration specifying the userdetails
throws:
ConfigurationException - if the user could not be instantiated |
| getLdapId | | public String getLdapId()(Code) | | Get the ldap id
the ldap id |
| initialize | | protected void initialize() throws ConfigurationException(Code) | | Initializes this user. The current (already authenticated) ldapId is
queried in the directory, in order to retrieve additional information,
such as the user name. In current implementation, only the user name is
actually retrieved, but other attributes may be used in the future (such
as groups ?) TODO: should the code be changed to not throw an exception
when something goes wrong ? After all, it's only used to get additional
info for display? This is a design decision, I'm not sure what's best.
throws:
ConfigurationException - when something went wrong. |
| setEncryptedPassword | | protected void setEncryptedPassword(String encryptedPassword)(Code) | | The LDAPUser doesn't store any passwords as they are handled by LDAP
Parameters:
encryptedPassword - is ignored |
| setLdapId | | public void setLdapId(String string)(Code) | | Set the ldap id
Parameters:
string - the new ldap id |
| setName | | public void setName(String string)(Code) | | LDAP Users fetch their name information from the LDAP server, so we don't
store it locally. Since we only have read access we basically can't set
the name, i.e. any request to change the name is ignored.
Parameters:
string - is ignored |
| setPassword | | public void setPassword(String plainTextPassword)(Code) | | The LDAPUser doesn't store any passwords as they are handled by LDAP
Parameters:
plainTextPassword - is ignored |
|
|