Knowledgebase
Security Module
Posted by on 24 March 2014 11:54 AM

In the security module ScriptCase, you can implement access rules for your system, thus creating a complete access system of control in your project. The validation can use an authentication with username and password, or use the LDAP resource, available starting from version 7 of Scriptcase.

 

 We'll show how to create the security module available at all levels.

 

 Since the ScriptCase version 6 has a specific section on the top menu, 'modules':

 

 

1. The first step is select the level of security that will be used.

 

 

Types:

 

  • User - Security level where the application is connected to user login, this level of security the user has access to all system applications.

  •  Application - Security level where the application relates to the user, this level of security the user only has access to certain applications.

  •  Group - Security level where the application relates to a group, this level of security is defined access each group a certain number of applications and each user is belonging to a group.

  •  LDAPLook this documentation about LDAP

 

 

2. Selecting the connection - The second step is common for any level of security used in this step you should select the connection that will be used by the security module.

 

 

 

Select connection:

 

  •  Connection - Select the connection to be used for the creation of the security module.

  •  Existing Tables - This option is used if already exists in your database the corresponding tables created by the security module.

  •  Create tables - You can choose the Scriptcase create new tables in your database.

  •  Tables Prefix - Prefix to create table names.

  •  Delete existing tables - This option should be used if you previously selected the Create tables option.

  •  Protect logged in users - Prevents the user to perform simultaneous logins, use the table of logged in users.

 

3. Joining tables - The third step is different for each security level, is used to associate the fields of the security module database fields with data. This step must be configured if you are using the "Existing Tables" option if you are using the "Create Tables" editing option in this step is because indisponíves ScriptCase already performs the association automatically.

Check how is this step for each security level.

 

NOTE: At the level, "Total Control LDAP", this step is equal to the security level User / Application. If you are using the option "LDAP authentication only", this step is not there.

 

-USER

 

Based on the security level of the user where the application is linked to the user login.

 

 

If using the existing tables option to perform the following configuration

 

User:

 

  •  Table - Set "User" table used by the system.

  •  Login - Set the field to stock user login.

  •  Password - Set the field to stock the user's password.

  •  Name - Set the field to store the user name.

  • Email - Set the field to store the e-mail.

  •  Active - Set the field to store whether the user is active or not.

  •  Activation code - Set the field to store the activation code.

  •  Administrator privileges - Set the field to store the user administrator privileges theme.

 

-USER/APPLICATION

 

Based on the security level of the application. Where the application relates to the user.

 

 

If using the existing tables option to perform the following configuration:

 

User:

  •  Table - Set "User" table used by the system.

  •  Login - Set the field to store user login.

  •  Password - Set the field to store the user's password.

  •  Name - Set the field to store the user name.

  •  Email - Set the field to store the e-mail.

  •  Active - Set the field to store whether the user is active or not active.

  •  Activation code - Set the field to store the activation code.

  •  Administrator privileges - Set the field to store whether the user has administrator privileges.

 

Application:

  •  Table - Set the table to store all project applications.

  •  Code - Set the field to store the code or the application name.

  •  Description - Set the field to store the description of the application.

  •  Application type - Set the field to store the type of application.

 

User/Application:

  •  Table - Set the table to store the relationship between the group and project applications.

  •  Login - Sets the field to store user login.

  •  Application Name - Set the field to store the name of the application.

  •  Access privilege - Set the field to store whether the user has privileges to access the application.

  •  Privilege insert - Set the field to store whether the user has the privilege to insert new records into an application.

  •  Privilege to delete - Set the field to store whether the user has privileges to delete records in an application.

  •  Privilege update - Set the field to store whether the user has the privilege to update the records in an application.

  •  Privilege export - Set the field to store whether the user has privileges to export records in an application.

  •  Privilege of print - Set the field to store whether the user has privileges to print the records in an application.

 

User/Group/Application:

 

Based security for Group level where access is defined for each group for certain applications.

 

 

If you are using the existing tables option to perform the following configuration:

 

User:

  •  Table - Set "User" table used by the system.

  •  Login - Set the field to store user login.

  •  Password - Set the field to store the user's password.

  •  Name - Set the field to store the user name.

  •  Email - Set the field to store email.

  •  Active - Set the field to store whether the user is active or not.

  •  Activation code - Set the field to store the activation code.

  •  Administrator privilege - Set the field to store whether the user has administrator privilege.

Group:

  •  Table - Set the table to store the groups created in the system.

  •  ID - Set the field that will store the code of the group.

  •  Description - Set the field that will store the group description.

 

Application:

  •  Table - Set the table to store all project applications.

  •  Code - Set the field to store the code or the application name.

  •  Description - Set the field to store the description of the application.

  •  Application type - Set the field to store the type of application.

 

User/Group:

  •  Table - Set the table to store the relationship between users and groups on a project.

  •  Login - Set the field to store your login.

  •  Group Code - Set the field to store the code of the group.

 

Group/Application:

  • Table - Set the table to store the relationship between groups and design applications.

  •  Group Code - Set the field to store the code of the group.

  •  Application Name - Set the field to store the name of the application.

  •  Access privilege - Set the field to store the group has privileges to access the application.

  •  Privilege Insert - Setting the field to store the group has privilege to insert a new record in the application.

  •  Privilege to delete - Set the field to store the group has privileges to delete records in the application.

  •  Privilege update - Set the field to store the group has privilege to update the records in the application.

  •  Privilege of export - Set the field to store the group has privileges to export the application records.

  • Privilege of printing - Set the field to store the group has privilege to print the records in the application.

 

4. Configuration - The fourth stage is used to inform the settings used in the security module.

 

This step is the same for all security levels

 

 

  •  Application prefix - Prefix of applications created by the security module.

  •  Encryption - Defines if the password encryption uses.

  •  Allow Security - Enables security on all applications in the project, provided that they are included in the security module.

  •  Using Captcha - Enables the option to use captcha on the login screen of the security module.

  •  Folders - Folder name in the project that will contain security applications.

  •  Theme - Theme used for security applications.

  •  Log - Log Sets the scheme that will be used in implementing security.

  •  Menu - Allows you to create or select an existing application menu in the project, to include a security module.

  •  Menu type - If you choose the option to 'Create Application menu, this option allows you to define the type of menu that will be created.

 

 

  •  Minimum - Minimum size of characters used by the user.

  •  Max - Maximum size of characters used by the user.

  •  Allowed characters - characters which define the end user can use.

 

 

  •  Send email with password - Defines whether the user can reactivate the password receiving it by email.

  •  Reset password, and send new email - Defines whether the user can reactivate the same password resetting and emailing.

  •  Send e-mail link for new password - Defines whether the user can reactivate the password resubmitting a link to the email with the registration of a new password.

 

 

  •  Allows the registration of new users - A link is created on the login screen, allowing new user registration.

  •  Require Activation Email - New users receive an activation link by email.

  •  Send e-mail to the administrator - When a new user is registered, the administrator will receive an email prior to allowing user access to the system.

 

 

  •  SMTP Server - Set the SMTP server.

  •  SMTP port - Set the SMTP port.

  •  SMTP User - Set the SMTP user.

  •  SMTP password - Set the SMTP password.

  •  SMTP Email - Set the SMTP email.

 

5. Insert data - Step five is used to insert data into Users and Groups table.

 

This step identical for all modules security, the only difference is in security group for this step adds the 'Group' field.

 

 

Insert data:

 

  •  Login - User login.

  •  Password - Password of the user.

  •  Name - user name.

  •  E-mail - E-mail user.

  •  Active - Enable user.

  •  Administrator privileges - Defines if the administrator has privileges (all features enabled).

 

This option exists only to create the security module by group:

 

Group - Group name that the administrator belongs.

 

6. Add application - The sixth stage is used to insert data into the table implementation.

 

This step is not necessary if you are using the security type "User".

 

 

Applications include - Selecting this option will insert ScriptCase the applications table security module all applications in the project

 

7. Profile - The last step is to save a profile in all settings used in the previous steps.

 

 

ou can save a profile for every user Scriptcase or just for the user of this project.

 

LDAP

 

See the LDAP documentation:

LDAP - Look this documentation about LDAP

(24 vote(s))
Helpful
Not helpful

Comments (3)
Magezi
01 August 2015 01:51 PM
Well explained I like it but what if you wanna make the security on data: defining the values for some fields that the user can insert,update,print,...

For instance you have to manage data of two entities(the entites are using the same applications and one database since some information are shared) in on database there are users of entity 1 and users of entity 2; the users of entity 1 are not suppose to make an action on the data of entity two and vice versa. so when a user wanna make an action you have to check if he has the right of performing that action on the data of the entity is acting on...
Gustavo Veras Sampaio
01 March 2016 05:44 PM
Hello Magezi! How are you?

It's a good point!
You can send us this suggestion to the e-mail : suggestion@scriptcase.com.br
Will be well received and we will analyze in detail, thank you!

Any question, i'm available!
Scriptcase Team


Gustavo Veras Sampaio
01 March 2016 05:48 PM
Hello Magezi! How are you?

It's a good point!
You can send us this suggestion to the e-mail : suggestion@scriptcase.com.br
Will be well received and we will analyze in detail, thank you!

Any question, i'm available!
Scriptcase Team


ScriptCase© - Todos os direitos reservados.
ERROR: This domain name (knowledge.netmake.com.br), does not match the domain name in the license key file suporte.scriptcase.com.br,support.scriptcase.net.

For assistance with your license, please contact the Kayako support team: https://support.kayako.com