What's new in Visual Guard

Visual Guard 3.2

For more information about a complete list of fixed bugs, improvements, breaking changes, see: Update List

What's new in Visual Guard 3.2

New Features the Visual Guard

• Group Management: you can now manage Groups of Users and grant them roles.
• Support for Silverlight: integration with Silverlight applications has been improved.See how to secure a Silverlight front end calling a WCF back end, here...
• Support for WPF: See How to Secure a WPF application here...
• Support for SharePoint: secure SharePoint projects like any other application. 
  Share users, roles and permissions across standard applications and SharePoint Projects
• Support for LINQ: See how to secure LINQ requests with Visual Guard
• Custom VG Roles: define your own VG Role and allow users to access some VG features across the VG WinConsole, VG WebConsole and VG API.
  
  

Spotlight on: Visual Guard User Groups

Visual Guard now supports hierarchical groups, both in WinConsole and in WebConsole. Here are some of the things you can do:

• Create/Read/Update/Delete groups through WinConsole, WebConsole and API.
• Hierarchical organization: Groups can contain users or groups.
• Group Permission Management: Roles can be related to any level of group and will apply to all users and groups within this group.
• Hierarchical Administration rights: When a user with the VG Administrator Role belongs to a group, their administration privileges are automatically restricted to the users and groups contained in this group.

 

Visual Guard WEB Console 2.0

• New group Module

 

Visual Guard Server pulic mode

With Visual Guard Server, you will be able to secure .Net applications that cannot directly access the Security database. The application will call Visual Guard Server to authenticate users and get their roles and permissions. Then, Visual Guard runtime will adapt the behaviour of the application to the user.

VG Server supports .Net-based applications embedding Visual Guard runtime.

VG server Public Mode is used in the following situations:

• Complex architecture (the application cannot connect directly with the repository)
• Applications developed with technologies other that .NET or PowerBuilder

 

For more information click here: Visual Guard Web Server.

 

See Also

How to integrate Visual Guard in a WCF application

Visual Guard expression language

Upgrading v3.1 to v3.2 

Upgrading v3.0 to v3.1 

Upgrading v2.8 to v3.0 

Upgrading v2.7 to v2.8