In order for Iron Speed Designer to generate role-based security code, it must know which database tables contain user name and password details as well as the roles.
|
|
|
Use the Application Security Wizard to set up page-based and component-based access control in your application. |
Role-based security is predicated on your application’s ability to know who the user is so that appropriate page access can be granted. This requires users to sign into the application, which in turn requires your database to contain user name and password information for users.
If you are implementing role-based security, Iron Speed Designer requires one table in your database to be designated as a “User Table”. The User Table contains a list of all of your application’s users and can be any table in your application. Within this table, you must have three important fields from which Iron Speed Designer builds the sign in mechanism in your application:
Any table in your database can be a User Table; there is no restriction on which table may be designated as a User Table or what other fields it needs to have other than those listed above.
|
An example table designated as a User Table. This table contains normal account information, including First Name, Last Name, and Address, as well as the required sign in information (shown highlighted). |
In the Application Security Wizard, make these selections:
As a matter of convenience, you may wish to set the Display Foreign Key As property for the Roles Table so that text descriptions of the roles are displayed in your application rather than the Role ID values.
Step 1: Select Application Security Type
Step 2: Enter Active Directory Connection String
Step 3: Select the User Table (Database Security)
Step 4: Select the Roles Table (Database Security)
Step 4: Select the Policy Store Role Provider (AzMan Security)
Step 5: Assign Page Permissions
Step 6: Configure Individual Components for Role-Based Security
Administering Database Security at Run-Time
Displaying Data for Logged In Users
Active Directory and Microsoft Authorization Manager Configuration