How to configure local accounts to allow users to access vpn based on the Device ID mapped to them?

03/26/2020 13 13739

DESCRIPTION:
How to configure local accounts to allow users to access vpn based on the Device ID mapped to them?

RESOLUTION:

Feature/Application:

How to configure local accounts to allow users to access vpn based on the device id mapped to them?

Procedure:
 
This is a new feature added in version 10.6.0 where local user accounts are mapped to their laptop's hard disk serial number. If a local user is mapped to his/her laptop HDD, he/she will be able to log into VPN from only his/her laptop and no other laptop / PC. Below are the steps to configure this setup. Prerequisites are, the Local Authentication server should be created and should be linked to required realm and End point Control (EPC) enabled.

STEP 1: Create a local account.
In AMC go to Users & Groups go to tab "Local Accounts" click "New" and select "User"
 

Provide the Username and desired Password. Open the Advanced tab which will show you the below options (Email address & Device Identifier). In this Kb article we are bothered about adding Hard Disk serial number as Device identifier. Below is an example.
 

Enter the serial number of hard disk and save it. We have now mapped the user with the HDD serial number. You can add as many users according to your requirement. You can also map a local user to as many device IDs as you want. The device IDs should be separated by a delimiter. The delimiter can be any character or a string, and the exact character or the string (including the white spaces) must be specified while creating the variables for device ID, which is explained in STEP2. Save settings.

STEP 2: Next step is to create variables. In AMC, go to "Resources" "Variables" and click on "NEW" which will take you to configuration window.
 

Provide a friendly name in the "Name:" text box (no white spaces in here) and under the "Type:" drop box select "User Attribute".
 

Description: Provide appropriate description if required.
Attribute: This field will be automatically filled by the appliance based on the option selected in the drop box below Attribute. Click on "All attributes" drop box which will give you the attributes present for the realm selected. For example: "local test" is a realm which is mapped to the Local authentication. Hence we get the two attributes "deviceId" and "primaryEmail". We are concerned about "deviceId" now.

Once we select deviceId, the attribute will be set to the same.

Output: There are 2 options here "Single result" and "Multiple results". Single result is used if you have configured a single Device Identifier. If you want to map a single local user to multiple Device IDs, then you can select option "Multiple Results" which will in turn enable the option "Delimiter".

Delimiter: This field must contain the same character or string that was previously specified while giving multiple Device IDs (HDD serial numbers).
NOTE: White spaces will also be counted as delimiter.

In the illustration is shown below, the delimiter used is semi-colon (;)
 

User: Go ahead and test the configuration by entering the user name from that particular realm. Here you can test with a local user. An illustration is shown below:
 

Save the settings. Now this variable will be valid for any device ID for that realm. The HDD serial number that is mapped with the local user will be substituted in this variable when that local user tries to login. The next step would be to use this variable in the Endpoint control device profiles.

STEP 3: EPC should be enabled. Create a new Device profiles (according to the OS environment) for Equipment ID. An example for windows OS is shown below.
 

Select the created variable and insert it as shown. Add the variable to current attributes and save the changes.
 

Create a standard zone and add this device profile to that zone. Save changes. Next step is to map the zone to the required community.

STEP 4: Select the required community and enforce the zone in "End Point Control Restrictions". Save changes and apply pending changes.

STEP 5: Test the VPN connectivity. If the user does not match with the mapped HSS serial number, he / she would be denied access.