Account administrators should use these instructions to enable and download the client for their account. 

1. (For Account Administrators only) In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure. 
2. (For Account Administrators only) Click SSL VPN. 
3. (For Account Administrators only) Click Members.
4. (For Account Administrators only) In the top bar, select the data center that corresponds to your virtual machine. 
5. (For Account Administrators only) Under Active Members, type and select your username or the username of your user.
6. Click Client.
7. In the top bar, select the data center that corresponds to your virtual machine. 
8. Click Download SSL VPN client. 
   • AMP will automatically detect your operating system; however, you can click Download for another platform to view other operating system options.
   • When you open the client, follow the on-screen installation instructions. 

   • Your SSL VPN login credentials are the same credentials you use to access the Armor Management Portal (AMP). 

     Note
     For Windows users, the client will download as a .zip file. Extract the installation files to your local hard drive. Launch the installer.exe file to begin the installation.

     Note

     For Mac OS users, the client will download as a .tgz file. Extract the installation files to your local hard drive. Access the mac_phat_client folder, and then run the naclient.pkg installer. When you run the installer, you will see an error regarding the certificate. Click Continue. (In a future release, Armor will resolve the issue.) To launch the SSL VPN client, in your Applications folder, search for naclient. If you run Mac OS 10.11 or higher, then please review Install SSL VPN Client for Mac OS, version 10.11 and higher.

9. After installation, open the client.
   • In the drop-down menu, default will be listed.
     Image Added
10. Click Settings.
    • To add a new connection, you must enter a Connection Alias, Hostname/IP Address, and Port, which you can find in AMP.
      Image Added
11. Return to AMP, specifically to the Client section of the SSL VPN screen.

12. Use the Client Configuration table to locate the data center and corresponding information to add to the client.
    Image Added
    
    

    Note

    If you see two entries for the same data center, then you must verify that you are using the non-recovery data center. To determine the correct data center: 1. In the left-side navigation, click IP Addresses. 2. In the top, drop-down menu, select the data center that does not contain the Recovery tag. 3. Take note of the displayed public IP address. 4. In the left-side navigation, click SSL VPN. 5. Under HOST/FQDN, verify the data center that contains the matching public IP address.

13. Under Client Configuration, copy the Location information, and then paste that information into Connection Alias.
14. Under Client Configuration, copy the HOST/FQDN information, and then paste that information into Hostname/IP Address.
    • Remove .vpc.armor.com.
    • Replace dashes / hyphens ( - ) with periods ( . ).
    • Remove any zero ( 0 ) that begins a section, such as 085 or 067.
    • For example, if you see in AMP 122-087-074-072, then in the client, you should enter 122.87.74.72.
    • In another example, if you see in AMP 122-087-074-702, then in the client, you should enter 122.87.74.702.

    • Original	Correct	Incorrect
      122-087-074-072.vpc.armor.com	122.87.74.72	122-087-074-072 122-87-74-72
      122-087-074-702.vpc.armor.com	122.87.74.702	122-087-074-702 122-87-74-72

15. Under Client Configuration, copy the Port information, and then paste that information into Port.
16. Click Add.
17. Click OK.
18. In the drop-down menu, select the newly created connection.
19. Log into the client.
    • Your SSL VPN login credentials are the same credentials you use to access the Armor Management Portal (AMP). 
20. If you have virtual machines in other data centers, then you must download the client for every data center you use. Repeat these steps for additional data centers.