An application contains a long list of permissions.
Managing these permissions is easier if you can split this list into several groups of permissions.

In Visual Guard, permissions folders are located in the Repository under the folder "Permission". This is the place where you create permissions and store them. You can create as many subfolders as you want to organize the permissions.

In the sample, we have created one folder per form. By default, we recommend defining subdivisions (or permission groups) for each major feature of your application (for instance, Product management, Customer management…). It will be easier tho find them again, when you will need to grant these existing permissions to users.

The permissions in this folder are not active.


Visual Guard

VG supports ASP.Net MVC.

We recommend to secure the controller or the Model part.

Are they any performance issues?

No significant performance issue has been observed while using Visual Guard. Net and ASP.Net MVC.


Visual Guard

yes. It can !

Yes it does.

Visual Guard allows you to define in the permission editor an expression that will change the property of a dynamic object at runtime. For example, you can hide a column in a dynamic datagrid. The expression is stored in the repository.


Dynamic Assemblies: You can secure applications loading assemblies dynamically (like applications using the Microsoft CAB framework). You can indicate the list of the assemblies in the property 'Other Assemblies' of the application in the console. Visual Guard .Net takes into account the main assembly and the referenced ones. Actually, Visual Guard .Net “sees” all objects involved in the compilation.

Visual Guard

As Iron Speed produces .Net code, ce code is supported by VG (any standard .Net components are supported).


Visual Guard

The 'Properties' property is considred as a component by Visual Guard and it is displayed in the treeview of the designer but not as a property in the property grid.To access to the 'TextEdit1.Properties.ReadOnly' in the security action designer, you have to:

* Select the 'TextEdit' node in the treeview in the right panel.
* Expand the node.
* Select the 'Properties' node.
* Enter 'True' in the 'ReadOnly' property item of the property grid in the right panel.


Visual Guard

Yes, Visual Guard is compatible with Microsoft Office SharePoint 2007.

For instance, you can develop a standard Webform application with Visual Studio.
This application will embedd VG run-time for authentication and permission purposes.
Then you can make it available through SharePoint.

The next question is : which system will manage user authentication?

For instance, you can let SharePoint manage user authentication and roles and map Sharepoint roles with VG roles.
When you will open the webform application (secured by VG) from SharePoint,
you will pass the current role to VG that will load and dynamically apply the corresponding permissions.


Visual Guard

VG can modify properties for Visual and Non visual Components. For instance, you may have a business object with a property called EnableCustomerList. VG can modify this property to “false” or “true”. The web service or business object will then take this property into account while responding to the client request.


Visual Guard

There are 4 options:

1rst. If the object is created statically:

You can change to "false" the property "visible" of the appropriate control, with a Visual Guard "Property Action", created with Visual Guard Console (no coding necessary). (dynamic permission)

2nd. This option consists in coding in a Visual Guard "Script action" (dynamic permission)
This action will execute this script on the appropriate event (for instance "RowCreated") and will change the property "visible" of the column.

Below is an example of script action executed on the event "RowCreated".
It will hide the buttons "Delete" for each rows of a GridView displayed in a webform.

GridViewRowEventArgs e = (GridViewRowEventArgs)eventArgs[1];
if (e.Row.FindControl("DeleteButton") != null)
{
((ImageButton)e.Row.FindControl("DeleteButton")).Visible =false;
}

This is another example of script action executed on the event "ItemCreated".
It will hide the first column of a DataGrid displayed in a webform.
DataGridItemEventArgs e = (DataGridItemEventArgs)eventArgs[1];
e.Item.Cells[0].Visible = false;

Where eventArgs[] is an array generated by Visual Guard when a script action is created.
This array contains the argument list of the event associated to the script action
In the example above, this array contains the arguments of the event "ItemCreated".

3rd option. If the object is created dynamically: (static permission)

You can create a property "col_x_visible" in your object, and you will test this property in your code to display or not this column. (static permission)

4th option: (static permission)
you can check in your program when the user have the permission to see this column.
For example, you can create a permission HidePersonalInformation for your application and you can test if the permission is granted to the current user in your application.

In the ItemCreated event of your datagrid, you can insert the following code:
if (VGSecurityManager.Principal.HasPermission("HidePersonalInformation"))
{
e.Item.Cells[0].Visible = false;
}




Visual Guard .NET

Both options are available with Visual Guard: In Visual Guard sample application, a filter is defined by modifying the property “Filter” (which filters rows already retrieved on the client). But it is also possible to modify the property containing the SQL query to add or modify a Where clause.



Visual Guard .NET

It is really easy. You use a technical action that modifies a Property (called “property action”). You can replace the value of the filter or add a condition to this filter. (for .net applications with dynamic permissions)

If you use static permissions, filters have to be coded in your program. In this case, your program will ask Visual Guard if the user has the appropriate permission. Visual Guard will reply and pass parameters depending on the current role. Your program will use these parameters value to compose the filter. (this process is easy).


Visual Guard

Two options:
* You can retrieve all rows from the stored procedure and filter them on the client.
* You can get from Visual Guard the value of the filter you want to apply and use this value as an argument in the stored procedure.


Visual Guard

It is possible to add parameters to a permission. In the .NET sample, there is a permission " display only information on a country" with a parameter "country" which specifies the country you want to display.
When this permission is linked to a permission set, you have to indicate the country (for example for the permission set UK HR employee the parameter is UK). This value may also be indicated by the program in run time.

Visual guard

There are several options:

1. It is possible to filter data of a dataview or change the "where" clause of an SQL Query by adding a security action that will change the Filter property of the object.

2. In some cases, you can test the permission in your code.

This example shows how to determine whether the permission "Display only information on a country" is granted to the current user and how to get the value of the argument "Country".

If Not VGSecurityManager.Principal.HasPermission("Display only information on a country") Then
MessageBox.Show("The current user can see all countries")
Else
Dim myPerm As VGIPermission = VGSecurityManager.Principal.GetPermission("Display only information on a country")
Dim myValue As String = CType(myPerm("Country"), String)
MessageBox.Show(String.Format("The current user can see only information about the country '{0}'", myValue))
End If


The following link shows the different ways to implement the security in your application:

http://www.visual-guard.com/visual_guard_doc/ApplySecurityInYourApp.htm

Visual Guard

Yes you can!

Visual Guard