Skip to content
Peter Girard edited this page Apr 18, 2017 · 3 revisions

An instance of the GPV can be configured for either public access or secured private access. For private access, users must first identify themselves to the GPV. The technical term for this process is "authentication". Once authenticated, private users are then given authorized access to secured parts of the GPV based on their roles.

Authentication Modes

The GPV supports four different modes of authentication.

An instance of the GPV can only be set to one of these modes. Two or more instances of the GPV having different authentication modes can share a single set of configuration tables, letting you manage both public and private capabilities from a centralized configuration.

Roles

The GPV has three built in roles:

  • public - Automatically assigned to all unauthenticated users
  • private - Automatically assigned to all authenticated users that have not been provided a specific role. Private users can access all publicly available parts of the GPV.
  • admin - The administrator role with access to the administrative tools and all secured parts.

You can create additional roles simply by specifying them for users in the GPVUser table. Users assigned to a specific role have also access to all secured parts marked for the private role as well as all publicly accessible parts.

Securables

Securable parts of the GPV are:

These tables provide an AuthorizedRoles field specifying all roles that are authorized to access the part as a comma-separated list. If left null, the part will default to public access. Setting AuthorizedRoles to "private" will allow all authenticated users to access the part, regardless of their specific roles.

Clone this wiki locally