The Auth:: class provides a common abstracted interface into the various backends for the Horde authentication system.
$Horde: framework/Auth/Auth.php,v 1.142.10.37 2009/10/26 11:58:58 jan Exp $
Copyright 1999-2009 The Horde Project (http://www.horde.org/)
See the enclosed file COPYING for license information (LGPL). If you did not receive this file, see http://opensource.org/licenses/lgpl-license.php.
Located in /Auth/Auth.php (line 80)
Class | Description |
---|---|
![]() |
The Auth_application class provides a wrapper around application-provided Horde authentication which fits inside the Horde Auth:: API. |
![]() |
The Auth_auto class transparently logs users in to Horde using ONE username, either defined in the config or defaulting to 'horde_user'. This is only for use in testing or behind a firewall; it should NOT be used on a public, production machine. |
![]() |
The Auth_composite class provides a wrapper around application-provided Horde authentication which fits inside the Horde Auth:: API. |
![]() |
The Auth_cyrus class provides horde with the ability of administrating a Cyrus mail server authentications against another backend that Horde can update (eg SQL or LDAP). |
![]() |
The Auth_ftp class provides an FTP implementation of the Horde authentication system. |
![]() |
The Auth_http class transparently logs users in to Horde using already present HTTP authentication headers. |
![]() |
The Auth_http_remote class authenticates users against a remote HTTP-Auth endpoint. |
![]() |
The Auth_imap:: class provides an IMAP implementation of the Horde authentication system. |
![]() |
The Auth_imsp class provides basic authentication against an IMSP server. |
![]() |
The Auth_ipbasic class provides access control based on CIDR masks (client IP addresses). It is not meant for user-based systems, but for times when you want a block of IPs to be able to access a site, and that access is simply on/off - no preferences, etc... |
![]() |
The Kolab implementation of the Horde authentication system. Derives from the Auth_imap IMAP authentication object, and provides parameters to it based on the global Kolab configuration. |
![]() |
The Auth_krb5 class provides an kerberos implementation of the Horde authentication system. |
![]() |
The Auth_ldap class provides an LDAP implementation of the Horde authentication system. |
![]() |
The Auth_login:: class provides a system login implementation of the Horde authentication system. |
![]() |
The Auth_pam:: class provides a PAM-based implementation of the Horde authentication system. |
![]() |
The Auth_passwd:: class provides a passwd-file implementation of the Horde authentication system. |
![]() |
The Auth_peclsasl:: class provides a SASL-based implementation of the Horde authentication system. |
![]() |
The Auth_radius class provides a RADIUS implementation of the Horde authentication system. |
![]() |
The Auth_shibboleth class only provides transparent authentication based on the headers set by a Shibboleth SP. Note that this class does not provide any actual SP functionality, it just takes the username from the HTTP headers that should be set by the Shibboleth SP. |
![]() |
The Auth_smb class provides an SMB implementation of the Horde authentication system. |
![]() |
The Auth_smbclient class provides an smbclient implementation of the Horde authentication system. |
![]() |
The Auth_sql class provides a SQL implementation of the Horde authentication system. |
An array of capabilities, so that the driver can report which operations it supports and which it doesn't.
The credentials currently being authenticated.
Hash containing parameters.
Applies a hook defined by the function _username_hook_frombackend() to the given user name if this function exists and user hooks are enabled.
This method should be called if a authentication backend's user name needs to be converted to a (unique) Horde user name. The backend's user name is what the user sees and uses, but internally we use the Horde user name.
Generates the correct parameters to pass to the given logout URL.
If no reason/msg is passed in, use the current global authentication error message.
Adds a set of authentication credentials.
Finds out if a set of login credentials are valid, and if requested, mark the user as logged in in the current session.
Clears any authentication tokens in the current session.
Checks if $userId exists in the system.
Attempts to return a concrete Auth instance based on $driver.
Generates a random, hopefully pronounceable, password. This can be used when resetting automatically a user's password.
Returns the currently logged in user, if there is one.
Returns the domain of currently logged-in user (e.g., bob@example.com would be returned as 'example.com').
Returns the curently logged-in user without any domain information (e.g., bob@example.com would be returned as 'bob').
Returns the requested credential for the currently logged in user, if present.
Formats a password using the current encryption.
Returns the name of the concrete Auth implementation.
Returns the URI of the login screen for the current authentication method.
Returns the logout reason.
Returns the status string to use for logout messages.
Returns the named parameter for the current auth driver.
Returns the name of the authentication provider.
Returns a salt for the appropriate kind of password encryption.
Optionally takes a seed and a plaintext password, to extract the seed of an existing password, or for encryption types that use the plaintext in the generation of the salt.
Queries the current Auth object to find out if it supports the given capability.
Is the current user an administrator?
Checks if there is a session with valid auth information. for the specified user. If there isn't, but the configured Auth driver supports transparent authentication, then we try that.
Return whether the authentication backend requested a password change.
Lists all users in the system.
Reads session data to determine if it contains Horde authentication credentials.
Applies a hook defined by the function _username_hook_tobackend() to the given user name if this function exists and user hooks are enabled.
This method should be called if a Horde user name needs to be converted to an authentication backend's user name or displayed to the user. The backend's user name is what the user sees and uses, but internally we use the Horde user name.
Deletes a set of authentication credentials.
Calls all applications' removeUser API methods.
Sets a variable in the session saying that authorization has succeeded, note which userId was authorized, and note when the login took place.
If a user name hook was defined in the configuration, it gets applied to the userId at this point.
Sets the requested credential for the currently logged in user.
Attempts to return a reference to a concrete Auth instance based on $driver. It will only create a new instance if no Auth instance with the same parameters currently exists.
This should be used if multiple authentication sources (and, thus, multiple Auth instances) are required.
This method must be invoked as: $var = &Auth::singleton()
Automatic authentication.
Updates a set of authentication credentials.
Authentication stub.
Driver-level admin check stub.
Documentation generated on Sun, 30 Jan 2011 05:15:19 +0000 by phpDocumentor 1.4.3