Project - LDAP Total Control

This LDAP authentication method allows the admin to select users from LDAP who will have access to the applications and which applications will be accessible for each user.

1. Connection - The connection will be used to create or associate the security module.

Image 1: Connection settings.

• Connection - Select a database connection from the project.
• Existing or Create Tables - You can choose if Scriptcase will create the tables in your database or it it will use existent tables.
• Table prefix - Prefix used to create the table names.
• Delete tables if they exist. - Delete the tables to create new ones.

2. Associate - It is just needed if you have selected the option to use "Existing Tables" in the previous step.

User:

• Table - Define the table "Users" used by the system.
• Login - Set the field to stores the User login.
• Password - Set the field to stores the User Password.NOT USED
• Name - Set the field to stores the User Name.
• E-mail - Set the field to stores the E-mail.
• Active - Set the field to stores if the user is active or not.
• Activation code - Set the field to stores the Activation code.NOT USED
• Administrator privilege - Set the field to stores if the user has administrator privileges.

Application:

• Table - Set the table to store all project applications.
• Application Name - Define the field to store the code or the application name.
• Description - Set the field to store the application description.
• Type of application - Set the field to store the application type.

User / Application:

• Table - Set the table to store the relationship between groups and project applications.
• Login - Define the field to store the User Login.
• Application Name - Define the field to store the application name.
• Access Privilege - Define the field to store if the user has privilege to access the application.
• Insert Prvilege- Define the field to store if the user has privilege to insert new records in the application.
• Delete Privilege - Define the field to store if the user has privilege to delete records in the application.
• Update Prvilege- Define the field to store if the user has privilege to update records in the application.
• Export Privilege - Define the field to store if the user has privilege to export records in the application.
• Print Prvilege- Defines the field to store if the user has privilege to print records in the application.

3. Configuration - This step will define the settings used on the security module.

General:

• Prefix applications - Create the security applications with a prefix in the name.
• Encryption - Define if the password will use encryption.NOT USED
• Enable Security - Enable the option "use security" in each application.
• Use Captcha - Enable the option to use CAPTCHA in the login screen.
• Folder - It creates a folder in the project to security applications.
• Schema - Define the theme to the applications.
• Log - Define the Log Scheme used in the security applications.
• Menu - It allows to create or select a Menu application to include the security module.
• Menu Type - Define the Menu type, if the option to create a new menu applications was set in the item above.

Login:

• Minimum size - Minimum size of characters typed by the user.
• Maximum size - Maximum size of characters typed by the user.
• Allowed Characters - Define wich characters the end-user can type.

E-mail Settings:

• SMTP Server - Define the SMTP server.
• SMTP Port - Define the SMTP port.
• SMTP User - Define the SMTP user.
• SMTP Password - Define the SMTP password.
• SMTP E-mail - Define the SMTP e-mail.

LDAP:

• Server - Define the LDAP server adress.
• Domain - Define the LDAP domain to be used.
• DN - Define LDAP's Distinguished Name to be used.
• Group - Define the LDAP Group to be used.

4. Test User - The fifth step is used to activate one user as administrator.

Insert Data Interface

Insert data:

• Login - Valid LDAP user Login.
• Password - Valid LDAP user password.
• Name - User name
• E-mail - User e-mail.

5. Add applications - The sixth step is used to populate the table Applications.

Add Applications Interface

Checking the option, Scriptcase will insert in the Applications Table, the name of each application existing in the project.

6. Profile - The last step is used to save in a profile all settings used on the steps to be used in other projects.

Profile Interface

You can save a profile to any Scriptcase user, just to that user or just to be used in that project.