Next Previous Contents

1. Generic fields

These fields appear no matter which library was chosen.

1.1 Module library

Shows the library selected for this entry.

This field is defined when the new entry is created, it can't be changed later.

1.2 Module type

Available options:


It's the part which identifies who the user really is.

It may just ask login and password, or may use biometric authentication (like voice pattern or a retina image), etc.


This part checks if the user is authorized to use the service he is authenticating into.

The accounting modules may check the authorized time, days, login origin, check for simultaneous logins, etc.


This service is used when password changing is desired.

For example, here may be used modules which check if the password is strong or weak.


The session part is responsible for creating the user environment.

It may grant access to some local devices such as audio or cd-rom, mount filesystems or log the system's events.

1.3 Control type

Available options:


This module's result directly affects the final result.

A failure on it will only appear after all the other modules being executed.


Much like 'required', but when an error occurs the other modules are not executed and the control returns immediately.


A failure on this module does not imply in authentication failure in a global way.

If the module fails, the next one of the same class is executed; if there's no next one the class returns successfully.


Modules tagged as 'optional' pratically do not have influence on the global authentication result. They have some influence if the previous modules of the same class do not have a definitive result.

1.4 Module parameters (opt.)

Parameters to be used with the library.

This field may appear or not. If not, usually other gadgets will appear according the selected library.

Next Previous Contents