The #Authent object implements a role-based user management with access protection. Like the #Password object, the password level principle (PWL) is used to implement access protection.
The difference to the #Password object is that a user is assigned a role and thus inherits the PWL of that role. The User/Password pair is also required for the login.
The Configuration of #Authent has to be accomplished with the following worksheets:
Parameters
Object
Column A
|
M/O
|
Default
|
Description
|
#Authent
|
M
|
|
Authent object
|
Text/File
Action
Column K
|
M/O
|
Default
|
Description
|
#page=<name>
|
O
|
|
#page=<name> is opened if an object is clicked that is protected (disabled) by the PWL
|
off
|
|
|
Objects that are protected by the PWL are fully hidden (off) instead of being displayed as disabled
|
ActionLimit1
Column N
|
M/O
|
Default
|
Description
|
#page=<name>
|
O
|
|
An incorrect password entry (login) initiates a screen page change to #page=<name>
|
ActionLimit2
Column N
|
M/O
|
Default
|
Description
|
#page=<name>
|
O
|
|
The page to change the password. Its gonna be opened when the current password has expired or after the first login.
|
Option
Column S
|
M/O
|
Default
|
Description
|
timeout=<time>
|
O
|
|
The current user is logged out after <time> minutes of no operation have elapsed.
• | <time> can be an integer constant. |
• | <time> can be a numerical variable. If it is not defined in UserVar or not yet registered, it is created as a WORD. |
|
keep_pwl
|
O
|
|
The current user is kept logged in if the password entry is incorrect, otherwise he is logged out.
|
bitwise=and
|
O
|
|
Links the PWL of the user or the bitwise and role with the PWL of the object (Option: pwl=<n>).
see also: #password
|
See also
|