addSecurity

Security is an integral part of every application that works with data and databases. Usually, applications that serve as a front-end to any database must have specific restrictions for each user to access data. Rights to work with data (read, write or change) are assigned by roles (security groups). A user can be granted permissions by inclusion in one or more groups (roles).

It is a developer’s task to create the roles and assign users to them, which involves extra effort in writing and debugging special code. In addition, any changes in security that may arise during application use creates the necessity for changes in program code with additional, often considerable, efforts.

The Add-In was created to automate the security task for developers and users. AddSecurity is intended for applications that interact with SQL Server. With the AddSecurity, a developer does not need to write any additional code to implement a security task. The administrators have the opportunity to assign users to any security roles in runtime without the developer’s assistance.

In addition to the add-in itself, the created security system has a database to store restrictions for all front-end applications and their users, and an ActiveX DLL that serves as a business server. This DLL implements login processes for the user, retrieves restriction data for the user in the application, and sends this data to application security functions inserted in the code by AddSecurity.

The security database is common for all applications using add-in AddSecurity and should be installed on the SQL Server before launching the first add-in for the Server. This can be accomplished by the SQL script supplied with the setup package.

The first step in working with AddSecurity is creating a list of roles for the application that the developer is working on in a special form in accordance with the end-user’s requirements. These roles for the application are saved in the security database.

AddSecurity uses the Extensibility Object Model in Integrated Development Environment for a graphical representation of all components in the active project. Usually it is launched at the last phase of development when all components in the application are already created.

The developer can put restrictions on any application component for any roles by marking component properties given for restriction in the role. The restriction data is saved in the security database and then used by the DLL in runtime to change default properties of the application components, depending on the roles the user is assigned to. The DLL has the form that allows authorized users and administrators to assign other users to various roles. Upon closing AddSecurity, a standard code module in the application is created, and necessary code lines in other application code modules are inserted.

AddSecurity Requirements:

Components	Notes
SQL Server 7.0 or later	For storage of Security Information (Roles, Users, Rights, Objects)
VB 6 standard edition or higher

Installation and useage:

1. Install AddSecurity on your PC.

2. Open VB project and through Add-in manager add this new Add-In.

3. Create all necessary forms with text box, labels, or other controls.

4. Run AddSecurity.

5. Enter login information for database to store security information:

If the Server doesn’t have a database for security information storage, you will receive a message and can immediately create this database.

6. AddSecurity will bring main screen to manage security for this project.

7. Select control and see all roles rights and all properties of selected control.

8. You can add/delete any role you need. To delete a role just remove the name of a role.

9. You can control access for any group using check boxes.

10. When you are finished, press the button with lock icon (Protection) and the system will create all necessary code.

11. AddSecurity will use a built-in login screen when user starts the program. The Developer doesn’t need to create it.

12. When you run your project AddSecurity calls a login screen automatically. As you can see this login screen is not part of your project.

13. AddSecurity can determine if you are an administrator of the SQL Server or this application, and if you are it will ask one more question:

14. If you go to the form <<Roles and Users>> you will be able to manage users and their roles for this application. You can even create a new login for the SQL Server.

Now when a user logs in to this application, AddSecurity will check which element of any form is accessible to this user, including Menu Items; that is why we did not create access level security for a form itself.

15. If you add a new form or control AddSecurity will notify you that all changes were added to the manager screen:

addSecurity

The security database is common for all applications using add-in AddSecurity and should be installed on the SQL Server before launching the first add-in for the Server. This can be accomplished by the SQL script supplied with the setup package.

The first step in working with AddSecurity is creating a list of roles for the application that the developer is working on in a special form in accordance with the end-user’s requirements. These roles for the application are saved in the security database.

AddSecurity uses the Extensibility Object Model in Integrated Development Environment for a graphical representation of all components in the active project. Usually it is launched at the last phase of development when all components in the application are already created.

back to top

AddSecurity Requirements:

Installation and useage:

1. Install AddSecurity on your PC.

2. Open VB project and through Add-in manager add this new Add-In.

3. Create all necessary forms with text box, labels, or other controls.

4. Run AddSecurity.

5. Enter login information for database to store security information:

If the Server doesn’t have a database for security information storage, you will receive a message and can immediately create this database.

6. AddSecurity will bring main screen to manage security for this project.

7. Select control and see all roles rights and all properties of selected control.

8. You can add/delete any role you need. To delete a role just remove the name of a role.

9. You can control access for any group using check boxes.

10. When you are finished, press the button with lock icon (Protection) and the system will create all necessary code.

11. AddSecurity will use a built-in login screen when user starts the program. The Developer doesn’t need to create it.

12. When you run your project AddSecurity calls a login screen automatically. As you can see this login screen is not part of your project.

13. AddSecurity can determine if you are an administrator of the SQL Server or this application, and if you are it will ask one more question:

14. If you go to the form <<Roles and Users>> you will be able to manage users and their roles for this application. You can even create a new login for the SQL Server.

Now when a user logs in to this application, AddSecurity will check which element of any form is accessible to this user, including Menu Items; that is why we did not create access level security for a form itself.

15. If you add a new form or control AddSecurity will notify you that all changes were added to the manager screen:

back to top