Posted  by  admin

Download Vpn Profile For Mac

-->

Purchase Nord VPN for Mac. HotSpot Shield. HotSpot Shield is a secure VPN which comes with ultra-fast VPN servers which comes with military grade encryption. Let’s look at the features of Hotspot Shield: It supports all platforms, so you can download Hotspot Shield and access on whichever device you want.

VPN client configuration files are contained in a zip file. Configuration files provide the settings required for a native Windows, Mac IKEv2 VPN, or Linux clients to connect to a virtual network over Point-to-Site connections that use native Azure certificate authentication.

  1. Cisco AnyConnect is the recommended VPN client for Mac. The built-in VPN client for Mac is another option but is more likely to suffer from disconnects. Overview Stanford's VPN allows you to connect to Stanford's network as if you were on campus, making access to restricted services possible.
  2. The Aviatrix VPN Client provides a seamless user experience when authenticating a VPN user through a SAML IDP. The client also supports password based authentication methods as well. The VPN Client can be installed on desktop platforms and is supported on various OS like Windows, Mac and Linux. Consult the VPN client user guide for how to use it.
  3. May 08, 2020.

Client configuration files are specific to the VPN configuration for the virtual network. If there are any changes to the Point-to-Site VPN configuration after you generate the VPN client configuration files, such as the VPN protocol type or authentication type, be sure to generate new VPN client configuration files for your user devices.

Download Vpn Profile For Mac
  • For more information about Point-to-Site connections, see About Point-to-Site VPN.
  • For OpenVPN instructions, see Configure OpenVPN for P2S and Configure OpenVPN clients.

Important

Starting July 1, 2018, support is being removed for TLS 1.0 and 1.1 from Azure VPN Gateway. VPN Gateway will support only TLS 1.2. Only point-to-site connections are impacted; site-to-site connections will not be affected. If you’re using TLS for point-to-site VPNs on Windows 10 clients, you don’t need to take any action. If you are using TLS for point-to-site connections on Windows 7 and Windows 8 clients, see the VPN Gateway FAQ for update instructions.

Generate VPN client configuration files

Before you begin, make sure that all connecting users have a valid certificate installed on the user's device. For more information about installing a client certificate, see Install a client certificate.

You can generate client configuration files using PowerShell, or by using the Azure portal. Either method returns the same zip file. Unzip the file to view the following folders:

  • WindowsAmd64 and WindowsX86, which contain the Windows 32-bit and 64-bit installer packages, respectively. The WindowsAmd64 installer package is for all supported 64-bit Windows clients, not just Amd.
  • Generic, which contains general information used to create your own VPN client configuration. The Generic folder is provided if IKEv2 or SSTP+IKEv2 was configured on the gateway. If only SSTP is configured, then the Generic folder is not present.

Generate files using the Azure portal

  1. In the Azure portal, navigate to the virtual network gateway for the virtual network that you want to connect to.

  2. On the virtual network gateway page, click Point-to-site configuration.

  3. At the top of the Point-to-site configuration page, click Download VPN client. It takes a few minutes for the client configuration package to generate.

  4. Your browser indicates that a client configuration zip file is available. It is named the same name as your gateway. Unzip the file to view the folders.

Generate files using PowerShell

  1. When generating VPN client configuration files, the value for '-AuthenticationMethod' is 'EapTls'. Generate the VPN client configuration files using the following command:

  2. Copy the URL to your browser to download the zip file, then unzip the file to view the folders.

Windows

You can use the same VPN client configuration package on each Windows client computer, as long as the version matches the architecture for the client. For the list of client operating systems that are supported, see the Point-to-Site section of the VPN Gateway FAQ.

Note

You must have Administrator rights on the Windows client computer from which you want to connect.

Use the following steps to configure the native Windows VPN client for certificate authentication:

  1. Select the VPN client configuration files that correspond to the architecture of the Windows computer. For a 64-bit processor architecture, choose the 'VpnClientSetupAmd64' installer package. For a 32-bit processor architecture, choose the 'VpnClientSetupX86' installer package.
  2. Double-click the package to install it. If you see a SmartScreen popup, click More info, then Run anyway.
  3. On the client computer, navigate to Network Settings and click VPN. The VPN connection shows the name of the virtual network that it connects to.
  4. Before you attempt to connect, verify that you have installed a client certificate on the client computer. A client certificate is required for authentication when using the native Azure certificate authentication type. For more information about generating certificates, see Generate Certificates. For information about how to install a client certificate, see Install a client certificate.

Mac (OS X)

You have to manually configure the native IKEv2 VPN client on every Mac that will connect to Azure. Azure does not provide mobileconfig file for native Azure certificate authentication. The Generic contains all of the information that you need for configuration. If you don't see the Generic folder in your download, it's likely that IKEv2 was not selected as a tunnel type. Note that the VPN gateway Basic SKU does not support IKEv2. Once IKEv2 is selected, generate the zip file again to retrieve the Generic folder.
The Generic folder contains the following files:

  • VpnSettings.xml, which contains important settings like server address and tunnel type.
  • VpnServerRoot.cer, which contains the root certificate required to validate the Azure VPN Gateway during P2S connection setup.

Use the following steps to configure the native VPN client on Mac for certificate authentication. You have to complete these steps on every Mac that will connect to Azure:

  1. Import the VpnServerRoot root certificate to your Mac. This can be done by copying the file over to your Mac and double-clicking on it. Click Add to import.

    Note

    Double-clicking on the certificate may not display the Add dialog, but the certificate is installed in the correct store. You can check for the certificate in the login keychain under the certificates category.

  2. Verify that you have installed a client certificate that was issued by the root certificate that you uploaded to Azure when you configured you P2S settings. This is different from the VPNServerRoot that you installed in the previous step. The client certificate is used for authentication and is required. For more information about generating certificates, see Generate Certificates. For information about how to install a client certificate, see Install a client certificate.

  3. Open the Network dialog under Network Preferences and click '+' to create a new VPN client connection profile for a P2S connection to the Azure virtual network.

    The Interface value is 'VPN' and VPN Type value is 'IKEv2'. Specify a name for the profile in the Service Name field, then click Create to create the VPN client connection profile.

  4. In the Generic folder, from the VpnSettings.xml file, copy the VpnServer tag value. Paste this value in the Server Address and Remote ID fields of the profile.

  5. Click Authentication Settings and select Certificate. For Catalina, click None and then certificate

    • For Catalina, select None and then Certificate. Select the correct certificate:
  6. Click Select… to choose the client certificate that you want to use for authentication. This is the certificate that you installed in Step 2.

  7. Choose An Identity displays a list of certificates for you to choose from. Select the proper certificate, then click Continue.

  8. In the Local ID field, specify the name of the certificate (from Step 6). In this example, it is 'ikev2Client.com'. Then, click Apply button to save the changes.

  9. On the Network dialog, click Apply to save all changes. Then, click Connect to start the P2S connection to the Azure virtual network.

Linux (strongSwan GUI)

Install strongSwan

The following configuration was used for the steps below:

  • Computer: Ubuntu Server 18.04
  • Dependencies: strongSwan

Use the following commands to install the required strongSwan configuration:

Use the following command to install the Azure command-line interface:

Generate certificates

If you have not already generated certificates, use the following steps:

Generate the CA certificate.

Print the CA certificate in base64 format. This is the format that is supported by Azure. You upload this certificate to Azure as part of the P2S configuration steps.

Generate the user certificate.

Generate a p12 bundle containing the user certificate. This bundle will be used in the next steps when working with the client configuration files.

Install and configure

The following instructions were created on Ubuntu 18.0.4. Ubuntu 16.0.10 does not support strongSwan GUI. If you want to use Ubuntu 16.0.10, you will have to use the command line. The examples below may not match screens that you see, depending on your version of Linux and strongSwan.

Free
  1. Open the Terminal to install strongSwan and its Network Manager by running the command in the example.

  2. Select Settings, then select Network.

  3. Click the + button to create a new connection.

  4. Select IPsec/IKEv2 (strongSwan) from the menu, and double-click. You can name your connection in this step.

  5. Open the VpnSettings.xml file from the Generic folder contained in the downloaded client configuration files. Find the tag called VpnServer and copy the name, beginning with 'azuregateway' and ending with '.cloudapp.net'.

  6. Paste this name into the Address field of your new VPN connection in the Gateway section. Next, select the folder icon at the end of the Certificate field, browse to the Generic folder, and select the VpnServerRoot file.

  7. In the Client section of the connection, for Authentication, select Certificate/private key. For Certificate and Private key, choose the certificate and the private key that were created earlier. In Options, select Request an inner IP address. Then, click Add.

  8. Turn the connection On.

Download Vpn Profile For Mac Desktop

Linux (strongSwan CLI)

Install strongSwan

The following configuration was used for the steps below:

  • Computer: Ubuntu Server 18.04
  • Dependencies: strongSwan

Free Vpn App For Mac

Use the following commands to install the required strongSwan configuration:

Use the following command to install the Azure command-line interface:

Generate certificates

If you have not already generated certificates, use the following steps:

Generate the CA certificate.

Print the CA certificate in base64 format. This is the format that is supported by Azure. You upload this certificate to Azure as part of the P2S configuration steps.

Generate the user certificate.

Generate a p12 bundle containing the user certificate. This bundle will be used in the next steps when working with the client configuration files.

Install and configure

  1. Download the VPNClient package from Azure portal.

  2. Extract the File.

  3. From the Generic folder, copy or move the VpnServerRoot.cer to /etc/ipsec.d/cacerts.

  4. Copy or move cp client.p12 to /etc/ipsec.d/private/. This file is client certificate for Azure VPN Gateway.

  5. Open VpnSettings.xml file and copy the <VpnServer> value. You will use this value in the next step.

  6. Adjust the values in the example below, then add the example to the /etc/ipsec.conf configuration.

  7. Add the following to /etc/ipsec.secrets.

  8. Run the following commands:

Next steps

Return to the article to complete your P2S configuration.

To troubleshoot P2S connections, see the following articles:

INSTALLING THE PULSE SECURE VPN CLIENT ON A MAC

Temporarily change your security preferences.
Before you can install the Pulse Secure client, you must temporarily change your Security preferences:

  1. Click the Apple Menu and choose System Preferences, then Security & Privacy.
  2. Click the padlock icon and enter your computer password.
    Note: If you are using a Smith-owned Mac that is bound to AD, enter your network password.
  3. On the General tab, change the Allow apps downloaded from: setting to App Store and identified developers.
  4. Leave the Security & Privacy window open for now.

Download the Pulse Secure Client.

  1. Download the Pulse Secure Client for Mac from the Smith Software site. Scroll down to the Misc. section.
  2. Double-click the pluse_v5.......pkg to start the install.
  3. Accept the defaults and if prompted, enter for your username and password to install new software.
  4. Restart your computer.

Configure a Connection to Smith

  1. Open Pulse Secure. A Pulse Secure icon (a fancy S for Secure) will appear in the top menu bar.
  2. From the Connection Bar, click the plus-sign to add a connection.
  3. The Type of Connection should read: Policy Secure (UAC) or Connect Secure (VPN)

  4. In the Name field, enter a name for your Profile (for example, Smith).
  5. In the Server URL field, enter vpn.smith.edu
  6. Click Add to save the profile.
  7. Click connect and login with your Smith username and password (do not include the @smith.edu to the username)
  8. You will be prompted to input a Secondary Password. This is to indicate the authentication method you want Duo to use. For a push to the Duo App enter Push, to have Duo call you enter Phone. For more information on this step please follow these instructions.

You are now using the Pulse Secure for a secure connection back to Smith.

Restore your Security preferences.

Return to the Security & Privacy window you modified in Part 1 to restore your previous settings:

  1. Change the Allow apps downloaded from: setting to Mac App Store and identified developers.
  2. Click the padlock icon to save your changes and prevent further changes.