Overview

Prior to Velocity 3.7 SP1 releases, the Velocity Web Service Client (VWSC) application used Anonymous Authentication mode which used the Forms Authentication Provider. As a result, when you initially hit the VWSC website, a login page displays and is authenticated by the Velocity web service.
Starting from Velocity 3.7 SP1 releases, the Administrator can disable Anonymous Authentication and define Windows Authentication to support Auto-login capability. For users logged in as an authorized Velocity operator in Velocity domain into Windows system on their device, the VWSC login page is by-passed to enable Auto-login feature.

Enabling Auto-Login Using Windows Authentication Provider

The VWSC application uses Anonymous authentication by default. To enable auto-login capability using Windows Authentication you must make configuration changes to the following:

• IIS configuration

• VWSC website configuration

• Velocity database

• Browser settings

Configuring IIS for Windows Authentication in Windows 10 and Windows Server 2016

Microsoft Windows 10

The steps below enable Windows Authentication in IIS where Velocity Web Client or VWSC bundle is installed.

1. Go to Control Panel → Programs.

2. Locate and click on "Turn Windows Features on or off" link as shown in figure 1.

Figure 1: Turn Windows Features ON or OFF in Programs

3. In Windows Features dialog, expand Internet Information Services→ World Wide Web Services→ Security to see the available options as shown in figure 2.

4. Select the following highlighted options(if not selected already), and then click OK as shown in the below figure 2.

Figure 2: Turn Windows Features ON/OFF

• World Wide Web Services→ Security→  Basic Authentication

• World Wide Web Services→ Security→  Request Filtering

• World Wide Web Services→ Security→  Windows Authentication

A progress dialog shows that Windows is building the selected feature changes.

5. Click Close after Windows completes the requested changes as shown in figure 3.

The Windows Authentication mode is enabled in IIS.

Figure 3: Completion of Requested Changes… 

Microsoft Windows Server 2016

The steps below enable Windows Authentication in IIS on Windows Server 2016 where Velocity Web Client or VWSC bundle is installed.

1. Go to Run and type ServerManager and press Enter or click Server Manager button in the Windows taskbar.
   
   The Server Manager Dashboard screen displays as shown in figure 4.

2. Click Add roles and features link in Dashboard.
   
   

   Open

   

   
   Figure 4: Server Manager Dashboard

3. Read the wizard instructions and click Next to continue as shown in figure 5.
   
   

   Open

   

   
   Figure 5:Before You Begin Menu

4. In Select installation type choose Role-based or feature-based Installation radio button as shown in figure 6.
   
   

   Open

   

   
   Figure 6:Installation Type Menu

5. Choose to Select a server from the server pool radio button as shown in figure 7.

6. Select the Windows Server 2016 from Server Pool and click Next.
   
   

   Open

   

   
   Figure 7:Server Selection Menu

7. Select the following highlighted options(if not selected already) and then click Next as shown in the below figure 8.

   1. Select Server Roles. Choose the following options under Roles:

      • Web Server (IIS) (20 of 43 Installed)→ Web Server (14 of 34 Installed) → Security (1 of 9 Installed)→ Request Filtering (Installed)

      • Web Server (IIS) (20 of 43 Installed)→  Web Server (14 of 34 Installed) → Security (1 of 9 Installed)→ Basic Authentication

      • Web Server (IIS) (20 of 43 Installed)→  Web Server (14 of 34 Installed) Security (1 of 9 Installed)→  Windows Authentication
        
        

        
        Figure 8:Server Roles Menu
        
        

Skip to the Confirmation menu in the Add Roles and Features Wizard as shown in figure 9.

8. In Confirm installation selections click Install to enable Windows Authentication on Windows 2016 Server as shown in figure 9.

Figure 9: Confirmation Menu
The Installation progress window display the progress of the Feature Installation as shown in figure 10.