Open topic with navigation

Project - Security Module

Making use of ScriptCase security resources you can implement access rules for the system being developed, further decreasing development time of a project, considering that ScriptCase will generate access applications and all validations automatically.

Image 1: Security Module Menu.


1. Type - The First step is used to select the level of security. There are three security levels and each level is based on a data model for storing information such as user accounts, passwords, access profiles, groups, etc.

Image2: Security Module - Type.




2. Select Connection - The second step is common for any type and it is used to select what database connection will be used to create the Security module.

Image 3: Security Module - Select Connection.

Select Connection:


3. Associate - The third step is different to each type of security level and it is used to associate the fields from the security module with the fields from the database. So it is just needed if you have selected the option to use "Existing Tables" in the last step.



6 - Logado:



4. Configuration - The fourth step is used to inform the settings used on the security module.


Image 7: Settings Interface

5. Insert data - The fifth step is used to populate the tables Users and Groups.


Image 8: Insert Data Interface

Insert data:


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

Note: This step is not needed if you are using the "User" security type.


Image 9: Add Applications Interface

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


7. Profile - The last step is for saving all settings in a profile so that they can be used in other projects.


Image 10: Profile Interface

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



See the LDAP documentation: