(Role Required: Owner, Administrator, Application Manager, Help Desk)

Administrators can protect an application in order to enhance security on those applications by using AuthX’s authentication factors.

Application Grid

The application grid lists application name, application type, policy assigned to the application and the groups who are assigned to the application.

1. Name: The name of the application is unique to the company.

2. Type: The application type is a category of the application.

3. Policy: The name of the policy which has been assigned to the application. Only one policy can be assigned to an application.

4. Groups: View Groups link opens a pop up which lists all the groups which are associated to the application. Multiple groups can be assigned to an application. If there were no groups assigned to the application, then the pop-up displays the following message- “No groups assigned. Application assigned.”

5. Actions – Allowing user to delete the applications

6. To edit an application, select the respective application from the grid on ‘Name’ column & you can make the required changes.

Protect an Application

(Role Required: Owner, Administrator, Application Manager)

1. An admin can protect an application by clicking on the Protect an Application button in the top right corner.

   

2. Before adding an application, please make sure to have an active user in the account

   1. Only then – you can protect an application (excluding LDAP and Microsoft Graph API applications.)

      

Application Components

Details lists important values used to protect an application.

1. Application ID – It is a unique id generated, which is static. The key can be copied by using the copy to clipboard icon.

2. Application Key – It is a unique key generated, which is static and hidden. The key can be copied by using the copy to clipboard icon. The admin must click to view the link to view the Application key. The Application key can copy and reset the key.

3. Application URL – The application URL of the application is generated dynamically from the domain they have logged into.

4. Admin Host name – The admin host name of the application is generated dynamically from the admin API.

5. Application Name – Application name is unique for a company and it is a mandatory field to protect an application.

6. Show this application on User Dashboard (Checkbox) – Only if this is enabled, this Admin application will be listed in the User Dashboard

7. Description

   1. Description field is to write the description of the application that is being protected.

   2. This is not a mandatory field.

8. Authentication Type – Mandatory field

   1. Passwordless Authentication

   2. Two Factor Authentication – Authenticate with different authentication factors

      

9. Application Configuration

   1. Download Services – While creating an application, user can download the services for following applications

      1. Open VPN

      2. Cisco VPN

      3. Radius

      4. WordPress

      5. LDAP

   2. Download Configuration – While editing an application, user can download the XML configuration file with Application setting details. This will be available for following applications

      1. Open VPN

      2. Cisco VPN

      3. Radius

      4. WordPress

      5. LDAP

      6. Windows

         

10. Policies

    1. Policies tab allows groups and policies to be added to the application.

    2. Group Policy

       1. In group policy, multiple groups can be assigned to an application by using the Apply application to groups button.

       2. On clicking upon the button, a pop-up lists all the active groups, which can be assigned to the application.

       3. If an admin doesn’t choose any group, then the application is applied is to all the active users in the company.

    3. Application Policy

       1. In application policy, a policy can be assigned to an application by using the Apply a policy button.

       2. On clicking upon the button, a pop-up lists all the active policies, which can be assigned to the application.

       3. If the admin doesn’t choose any policy, then the default global policy is assigned to the application.

       4. Admin can choose only one policy per application. (Radio Buttons). The admin should be able to deselect a radio button (that is, not choose any options).

       5. The chosen policy name is displayed before the apply a policy button. If no policy is chosen, then the default global policy is displayed before the apply a policy button.

       6. Upon clicking the policy name, the admin should be able to just read the policy and not edit. That is, there should be no save button.

    4. Authentication Workflow

       1. If multiple authentications are required for this application, then you can create a workflow in Settings & assign the same. For more details, refer here

Reading an application

(Role Required: Help Desk)

Admin with role Help Desk can only read the applications that have been protected. They click on the application name in the applications grid. They see the application components, but they cannot edit any components. Therefore, there is no save button and the Apply application to groups and Add a policy button should be disabled. They can click on the policy name just to read the policy.