Self Service VPN Integration

Self Service VPN gives you the power to view and manage IPsec VPN connections from your Appian Cloud environment to other resources through Cloud Resources in MyAppian.

Please review the Appian Cloud VPN Integration documentation to get familiar with Appian Cloud VPN before configuring a VPN connection using the Self Service functionality.

Prerequisites

  • You need an Appian Forum account.
  • You need to be a support contact. A support contact has the ability to create Support cases.

Considerations

Currently, Self Service VPN only allows you to manage a single, static, policy based VPN connection to a server in your cloud environment. If you need to have multiple tunnels per server, DNS-based VPN, or Dynamic VPN, please open a Support case, and we will help you to configure it per the Appian Cloud VPN Integration documentation.

How to configure a new VPN tunnel

To configure a VPN connection:

  1. Visit MyAppian and click CLOUD RESOURCES.
  2. In the Connectivity subsection, click VPN Configuration Details.
  3. If there are no existing VPN configurations for your server(s), click Add a connection to begin the configuration process.
  4. Select the appropriate server and fill out the following data:
    • Connection Name: Alphanumeric string to identify the connection.
      • The Connection Name should be unique per server.
    • Your Gateway IP: The public IP of your VPN device to establish the IPSEC connection.
    • Your Subnets: Specify all the subnets that the Appian server will connect to in your network.
      • The format should follow the CIDR notation (i.e 192.168.1.0/24).
      • To add a single IP, be sure to include a /32 at the end of the IP (i.e 192.168.1.1/32).
      • The subnets that are added cannot be part of the restricted Appian Subnets. Please review Reserved IP Address Ranges for more details.
    • Pre-Shared Key: Key to establish the initial security association.
      • Should be an alphanumeric, 40 character long string.

        IMPORTANT: Keep a backup of the pre-shared key; it will not be accessible after submitting the form.

  5. If necessary, configure the advanced options.
  6. After setting all required values in the form, click Add.
  7. Confirm to apply your changes and start your tunnel and click Finish.

You will be taken back to the VPN Configurations Details page and see your new connection was added for the chosen server in your cloud environment. Both the Appian Gateway IP and the Appian Network Interface IP have been assigned, and the next step for you would be to configure the VPN tunnel from your side.

The VPN tunnels are configured to accept your connection as soon as you start the connection from your VPN device. You can check the status of your connection by reviewing the IPSEC logs of your connection. See Appian Cloud Web Administration to understand how to access these logs.

The IPSEC log files will have the following format ipsec.log.YYYY-MM-DD (i.e ipsec.log.2020.01-01) and will only be kept for seven days at a time.

Advanced options

If you want to customize the specifics of your VPN connection, there is an advanced options section that can be expanded. The following fields and their default values will be used if no changes are made.

  • Appian Network Interface IP: The endpoint IP for your Appian server.
    • If no IP is provided, we will automatically assign an IP in the 172.30.0.0/24 subnet to your server.
    • If you do not want an IP in the 172.30.0.0/24 range, you can input an IP.
    • Your IP cannot be a part of the Appian restricted IPs. Review Reserved IP Address Ranges for more details.
  • IKE Version: IKEv1 or IKEv2 (Default IKEv2)
  • Perfect Forward Secrecy: Determines whether or not new keying material will be generated for each IPsec SA. (Default: PFS enabled).
  • Phase 1 Encryption Algorithms: The encryption algorithms supported for the VPN tunnel for phase 1.
    • Supported values aes128, aes256, aes_gcm_c128 and aes_gcm_c256. (Default aes256).
  • Phase 1 Hashing Algorithms: The hashing algorithms supported for the VPN tunnel for phase 1.
    • Supported values sha1 and sha2_256. (Default sha2_256).
  • Phase 1 Diffie-Hellman Groups: Supported values: dh14, dh15, dh16, dh17, dh18, dh19, dh20, dh21, dh13 and dh24. (Default dh14).
  • Phase 1 Lifetime: How long the keying of a connection (IKE) should last before being renegotiated. (Default 28800 seconds)
  • Phase 2 Encryption Algorithms: The encryption algorithms supported for the VPN tunnel for phase 2.
    • Supported values aes128, aes256, aes_gcm_c128 and aes_gcm_c256.
    • If an AEAD algorithm is selected (aes_gcm_c128 or aes_gcm_c256), hashing is already included, and as a result, a hashing algorithm cannot be chosen. (Default aes256)
  • Phase 2 Hashing Algorithms: The hashing algorithms supported for the VPN tunnel for phase 2.
    • Supported values sha1 and sha2_256. (Default sha2_256).
  • Phase 2 Lifetime: How long an instance of a connection should last, from successful negotiation to expiry. (Default 3600 seconds)
  • DPD Action: Dead peer detection (DPD) action. Defines what action to take when a DPD peer is declared dead. Supported values:
    • restart (default): Restart the IKE session when DPD timeout occurs.
    • hold: The IKE session will stay in hold status.
    • clear: End the IKE session when DPD after timeout.
  • DPD Delay: Length of time between dead peer detection keepalives that are sent for this connection. (Default 30 seconds)
  • DPD Timeout: Length of time that the connection idles without hearing back from the other peer. (Default 120 seconds)

How to modify an existing VPN tunnel

To configure a VPN connection:

  1. Visit MyAppian and click CLOUD RESOURCES.
  2. In the Connectivity subsection, click VPN Configuration Details.
  3. If your connection is supported for modification, inside of a connection’s details you will be able to click Modify to begin the modification process.
  4. You should always be able to modify the following:
    • Connection Name
    • Your Subnets
    • Pre-Shared Key
  5. If your connection is fully supported for modification, you’ll also be able to modify the following advanced options:
    • IKE Version
    • Perfect Forward Secrecy
    • Phase 1 Encryption Algorithms
    • Phase 1 Hashing Algorithms
    • Phase 1 Diffie-Hellman Groups
    • Phase 1 Lifetime
    • Phase 2 Encryption Algorithms
    • Phase 2 Hashing Algorithms
    • Phase 2 Diffie-Hellman Groups
    • Phase 2 Lifetime
    • DPD Action
    • DPD Delay
    • DPD Timeout
  6. After setting all required values in the form, click Modify.
  7. Confirm to apply your changes and restart your tunnel and click Finish.

You will be taken back to the VPN Configurations Details page, and you will see one of the following:

  • If your connection is being configured in your server, you will see a banner in your connection’s details indicating so and modification of the connection will be temporarily disabled
    • Use the refresh button to verify the status of the configuration change. It should not take longer than a few minutes.
  • If your connection had problems being configured, you will see a banner in your connection’s details indicating so. No further modifications will be allowed, please contact Appian Technical Support if you run into this scenario.

FAQ

How do I configure VPN tunnels for high availability sites?

You can add a connection for each server by following the steps mentioned in the How to Configure a VPN Tunnel? section.

Can I configure failover using self service VPN?

It is not possible to configure failover using the Self Service VPN interface at this time. If necessary, you can open a Support case, and we will help you to configure failover tunnels for your environment.

I need to modify a VPN tunnel, and I am unable to do so through self service VPN. What should I do?

Open a Support case and our support team will help you to modify a tunnel.

Who can view, add or modify VPN configurations?

Self Service VPN functionalities are only available to authorized technical support contacts for the account the environment belongs to.

Open in Github

On This Page

FEEDBACK