Why reuse Windows Accounts?

1. You already have a user list in Active Directory, and want to save the time of creating a whole new user list.
2. You want to manage a single user list in Active Directory and keep maintenance costs low (by not maintaining two or more identical user lists).
3. You want to implement single sign-on authentication in your .Net applications.
4. You want to combine windows authentication and role based permissions
   

How to declare Windows Accounts in the Console:

Visual Guard .Net provides a ready-to-use search window to find users or groups in Active Directory.
When you select Windows Accounts or Groups, Visual Guard .Net stores the user's security identifier (SID) the Visual Guard repository (security Database).
You can declare as many users as you need at a time.

Once declared, the user or group appears in Visual Guard .Net user list.
You can then assign Visual Guard .Net roles and permissions to this user.

Integration with Active Directory:

A key advantage of Visual Guard .Net is the extremely light integration process.
It consists in 1 copy/paste operation.
It allows implementing security without delay.

For the integration with Active Directory please see this Flash demonstration

	Windows Authentication Form Based Authentication Advanced

You want to use authentication based on a username/password combination, but don’t want to start from scratch.
You need a ready-to-use, comprehensive identity management and permissions solution for .Net applications.

Visual Guard .Net has its own authentication mechanism supporting ASP.NET, Winform, WCF, Webservices...

A proprietary membership provider allows the creation and management of user accounts and passwords.
Credentials are stored in the Visual Guard .Net Repository.
A user-friendly wizard allows granting users with roles in a few clicks.

With Visual Guard .Net, you can define a password policy for Visual Guard .Net accounts.

A dedicated wizard allows adapting password policy to your security requirements:

• Minimum password length
• Minimum number of non-alphanumeric characters
• Rules for reusing previous passwords
• Rules for enforcing a unique email address for each user
• Rules for enforcing a new password every x days
• Maximum number of consecutive failed attempts to enter a password. When the maximum is reached, the user ID will be disabled until reset via an authorized process.
• Number of grace logins (ability to log in x times after the account is blocked).
• And more…

Regular expressions are available to customize the verification of the password. You can also define a list of compulsory characters (for example, at least one uppercase letter, one lowercase letter, and at least one number), a list of valid/invalid characters, etc…

Single sign-on
Off-line Mode authentication
Mixed mode authentication
Multi-user desktop authentication

The concept of Single Sign-On is to ask users their credentials only once, at the moment they log in to their Windows session. Once authenticated, they will not be asked for their credentials again, and will be able to access any authorized resources.
Visual Guard will automatically apply the permissions linked to their roles.

Why?
Keep your application safe AND user-friendly. End users will not have to authenticate again and again, and you have assured the highest level of security.

How?
Visual Guard .Net supports Windows authentication. It automatically implements the Windows single sign-on process.
When a Windows user declared in Visual Guard .Net opens an application, his SID is identified. Visual Guard retrieves and applies his roles and permissions.

The concept of Offline mode is to secure the access of a user, even if the application cannot access the server and repository.

Why?

In case of mobile end-users, there is no direct access to the Database.
This means no access to the VGRepository and the permissions.


How?
In this configuration, you activate VGOffline mode. When the end user connects to the DB, VG will enable and update the VGOffline Store. It will act as the repository any time the end user connects to the application without connection to the Database.
As soon as there is a connection to the DB, the VGOffline Store synchronizes with the VG Repository. The Roles, permissions, and the log are updated.

Visual Guard .Net can manage several authentication modes for a given application application (ASP.Net, Winform, WCF, Webservices...).
The same application can be accessed by users authenticating against either Active Directory or Visual Guard.

For example an ASP.NET website can be accessed by both employees (authenticated against AD) and customers (authenticated against VG). Visual Guard .Net will apply roles and permission equally well for Windows and username/password accounts.

Visual Guard .Net enables you to define a multi-user desktop among a network of Single User Sign-On machines.
On their personal desktop, users are under single sign-on process to maximize productivity.
On this particular desktop, users are required to authenticate for maximum security.

Try Visual Guard .Net now!