The FlashConnect, authentication process uses three files:
w3Users
w3Groups
w3Apps
The authentication process differs for static and dynamic applications:
Static. FlashConnect authentication is not necessary since static Web pages do not interact with the database. FlashConnect static applications do not appear in the w3Apps file. Only the standard Web server based authentication, as explained above, is available.
Dynamic. Dynamic Web pages that do interact with the database may require group level and/or user level authentication. When a request comes in to a FlashConnect server to run an application, these checks are made:
Step |
Check |
Yes |
No |
1 |
Does the application specified in the w3Exec variable exist in w3Apps file? |
Step 2 |
Error display |
2 |
Is this an anonymous application? |
Step 8 |
Step 3 |
3 |
Is the user name valid? |
Step 4 |
Logon display |
4 |
Is the user’s password correct? |
Step 5 |
Logon display |
5 |
Does the user field of w3Apps record contain "all"? |
Step 8 |
Step 6 |
6 |
Is the user allowed to use the application? |
Step 8 |
Step 7 |
7 |
Does one of the groups this user belongs to match one of the groups that can run this application? |
Step 8 |
Logon display |
8 |
Is there an account name and password specified in the w3Apps item? |
Log to that account. Step 9 |
Step 9 |
9 |
Run the application. |
|
|
See Also