Table of Contents
Authentication management can be used to authenticate a session, that is, to identify the user at the client side of the session.
Authentication is done inline, with HTML forms, not with HTTP authentication (that's the browser popup you get when you hit a page protected with htaccess). Inline authentication has several advantages over HTTP authentication:
Accessible instance variables
| classname | Serialization helper: The name of this class |
| persistent_slots | Serialization helper: The names of all persistent slots. |
| lifetime | Maximum allowed idle time before the authentication expires. |
| refresh | Maximum allowed time before the authentication info (perms and alike) are re-read from the database calling auth_refreshlogin() method. If set to 0 authentication info are read only at the login stage. |
| mode | Authentication mode: log or reg (see below). |
| database_class | A classname. Auth uses this class to make a database connection. |
| database_table | Database table used to keep the session variables. |
| magic | An arbitrary value used in uniqid generation. |
| nobody | Flag: If true, we use default authentication. |
| cancel_auth | The name of a button that can be used to cancel a login form. |
Internal instance variables