<![CDATA[Novalys]]> <![CDATA[Where is Visual Guard .Net installed?]]> Where is Visual Guard .Net installed?

Administration console:
The Administration console is installed on developers and administrators desktops.

For the application:
You need to add the Visual Guard .Net assemblies to the dotnet application, plus two configuration files and deploy them along with the application.

For the repository
Visual Guard .Net creates the repository in a Database (Oracle 9i and higher or SQLServer 2000 or higher). This Database must be accessible from the dotnet application.



Visual Guard .NET

 

]]> <![CDATA[What VG modules are added to the applications?]]> What modules are added to the final application, when this one is managed by Visual Guard .Net?

Visual Guard .Net assemblies are deployed along with the application assemblies.
Visual Guard .Net repository depends on the type of storage you choose : most users create Visual Guard .Net repository tables in their application database.
So they just keep deploying their database, which is enough for Visual Guard .Net repository to be accessible.

]]> <![CDATA[How to manage several list of user/roles in one install?]]> If we are hosting multiple web sites on a single machine,on behalf of multiple customers, we'd need to have the ability to have completely separate user and role sets for each site. Of course it would be nice if all of this were done with a single install of the product and its database.

Would that be possible?

You can secure as many dotnet applications as you want in Visual Guard .Net. You can secure them each in one different repository, with separate list of users and separate list of roles.
This is done with only one install of Visual Guard .Net and its database.

]]> <![CDATA[Our app is locked, how can we give clients admin rights?]]> We are a softwarehouse and the product we want to secure is a locked application. we do not have access to the source code. How can we give the end user the right to create users and give them roles?

You can use either the console with the role "Restricted User administrator".
This role allows to manage users and roles of the applications for which the user is a member of "membership manager" role.

Or you can use the API to create your own administration form and manage users and roles.


Visual Guard .NET - Version 2.7.806.18

]]> <![CDATA[How to integrate Visual Guard in our application?]]> In Visual Guard, are there DLL's that we would compile against containing the functions that would be called which in turn access the database?

Visual Guard has his assemblies(DLL) which you need to refer in your application, which in turn will access to VG database to perform action. This assembly also contains API which has tons of methods to communicate with Visual Guard features like CreateUser, UpdateUser, GetRoles, AssignRoleToUser, etc. Through API, you can explicitly perform action in your application.

]]> <![CDATA[How Novalys helps you to evaluate Visual Guard?]]> 1 - Visual Guard is a modular and flexible solution that can be:

  • Implemented as a ready-to-use system
  • Used as a security Framework to build a custom access control system.
    It has been designed to comply with most technical and functional requirements.

2 - By default, we go through a standard process to assist projects in the evaluation and validation of Visual Guard.
We can follow this process for your application, unless you prefer to proceed otherwise.

  1. You can consider this discussion as a first step to design the right system upon your context.
  2. Then, we could arrange a conference call, to review the suggestions and questions raised at this point.
  3. Finally, we assist you to develop a simple prototype, based on a sample code reproducing your targeted architecture, and secured by Visual Guard.
    This prototype will be used as a proof-of-concept, as well as a template for the developers that will implement Access Control in the application.
]]> <![CDATA[how does Novalys handle the support during development time?]]>
  • For basic architecture (Winform apps or simple asp.net website for instance), development team can implement VG as a ready-to-use solution.
    In this case, they follow the developer's guide and use some default settings.
    They may ask questions by email about Visual Guard's features and configuration, but in most cases they need little assistance.
  • For other architectures and/or complex access rights definition and assignment, we usually stay close to the development team until the application goes to production.
    • First, we discuss with the architect and developers to understand their technical & functional specs.
    • Then, we assist you to build a prototype to design and validate the best solution available to comply with these specifications
    • Developers use this prototype to secure their application, as well as the standard Visual Guard literature
    • When questions come along the development process, we organize web meetings:
      it allows us to see the developer's environment and work with him directly on his environment to fix any issue.

     

    ]]>