From 488bc60e3e84096ee2a58471c8028cb3c682b371 Mon Sep 17 00:00:00 2001 From: xue <> Date: Fri, 9 Mar 2007 20:21:01 +0000 Subject: added TDbUserManager and TDbUser. --- .../quickstart/protected/pages/Advanced/Auth.page | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) (limited to 'demos/quickstart/protected/pages/Advanced') diff --git a/demos/quickstart/protected/pages/Advanced/Auth.page b/demos/quickstart/protected/pages/Advanced/Auth.page index 2c335f88..c8380901 100644 --- a/demos/quickstart/protected/pages/Advanced/Auth.page +++ b/demos/quickstart/protected/pages/Advanced/Auth.page @@ -89,4 +89,32 @@ We have seen in the above example that two users are specified in the applicatio

where the roles attribute in user element is optional. User roles can be specified in either the user element or in a separate role element.

+ +

Using TDbUserManager

+

+TDbUserManager is introduced in v3.1.0. Its main purpose is to simplify the task of managing user accounts that are stored in a database. It requires developers to write a user class that represents the necessary information for a user account. The user class must extend from TDbUser. +

+

+To use TDbUserManager, configure it in the application configuration like following: +

+ + + + + + +

+

+In the above, UserClass specifies what class will be used to create user instance. The class must extend from TDbUser. ConnectionID refers to the ID of a TDataSourceConfig module which specifies how to establish database connection to retrieve user information. +

+

+The user class has to implement the two abstract methods in TDbUser: validateUser() and createUser(). Since user account information is stored in a database, the user class may make use of its DbConnection property to reach the database. +

+
$Id$
\ No newline at end of file -- cgit v1.2.3