Create UDP and TCP applications

Download, configure and use EAA Client for UDP or TCP applications.

These steps are completed by both an Enterprise Application Access (EAA) administrator and the users. First you enable the client in the identity provider (IdP). Next, you can add and configure a TCP-type or Tunnel-type client-access applications.

To install the EAA Client, users or you can download and install it from the Login Portal. By default, the Login Portal presents a download option that is specific to the user's operating system. A user completes the steps in this procedure. You can also download the client from the Login Portal to distribute it to users across their organization. Depending on the operating system, download and install the client:

  1. Install the EAA Client.

  2. Configure EAA Client.

  3. Connect to TCP and UDP applications.

Enable EAA Client in an identity provider

The setting to enable EAA Client is done in an ​Akamai​ or third-party identity provider (IdP) configuration in Enterprise Application Access. By default, the setting to enable EAA Client is disabled. You must enable before you configure a TCP-type or Tunnel-type client-access application.

πŸ“˜

You can only enable the EAA Client on one identity provider.

  1. Log in to Enterprise Center.

  2. In the Enterprise Center navigation menu, select Application Access > Identity & Users > Identity Providers.

  3. Select the identity provider to open it.

  4. In Client select Enable EAA Client.

  5. Select Akamai Cloud Zone. The cloud zone should be a geographic location closest to the data center where your application resides.

  6. Click Save.

  7. Deploy the identity provider.

Add a TCP-type client-access application

Add a TCP-type client-access application to EAA Client and configure it's parameters.

  1. Log in to Enterprise Center.

  2. In the Enterprise Center navigation menu, select Application Access > Applications > Applications.

  3. Click Add Application (+).

  4. In Type select Client-Access App. In Mode select TCP mode (single port, port mapping, load-balancing options).

  5. Enter application name and optional description.

  6. Click Add Application.

  7. In App Settings > Settings configure the following:

    • Application Host. Enter the hostname of the client access application. This is the hostname that the native client uses to communicate with the application or application server. For example, if you are configuring a client like Outlook, this would be the hostname that is associated with Outlook accounts in your organization such as mail.mydomain.com and is used to communicate with Microsoft Exchange.

    • Port. Specify the same port number, as you are going to add for the application App Server IP/FQDN. The EAA Client listens for traffic on this port from the user's computer.

    • Endpoint Host. Enter the external host of your application. This is the cloud endpoint for all communications between the client access application and Enterprise Application Access. Additionally, choose one of the following:

    • Use your domain. If you use your own custom domain, you must provide a certificate configured as a complete bundle with all the subordinates (having the full chain of trust), otherwise you will see a web-socket error. To use an uploaded certificate, select Use uploaded certificates and select the previously uploaded certificate.

    • Use Akamai domain. If you use an ​Akamai​ domain no certificate is needed. For example, Akamai domain.

    The cloud zone should be a geographic location that is closest to the data center where your application server resides. It is in the Client-*form, for example Client-US-East, Client-US-West. Enter closest location to the application in the data center.

  8. Optionally, you can add an application category for the app.

  9. Click Save.

  10. To add connectors to the application select Connectors.

    πŸ“˜

    More than one connector is recommended for high-availability and load balancing.

  11. Click Associate connector and select one or more connectors, and click Associate.
    To remove a connector, click Disassociate next to it.
    The associated connector appears in Connectors.

    πŸ“˜

    The connector should run to deploy the application.

  12. To add Application Server IP/FQDN to the application configure the following:

    • Server IP/FQDN. Enter the IP address or fully qualified domain name (FQDN).

    • Port. Specify the port of the TCP application. It should be the same port number as you entered in previous steps.

To configure multiple applications servers for load balancing, click Add New Server (+). Enterprise Application Access supports various load balancing techniques including round-robin, session or cookie stickiness, and source IP hash in Advanced tab.

  1. To add authentication to the application in Authentication enable Authentication.

  2. For Identity provider, select an identity provider from the list.

  3. Click Assign Directory and select one or more directories from the list.

  4. Click Associate.
    The directory appears in Assigned Directories.

  5. To add an access control rule (ACL) to the application in Access enable Access.

    1. To create a new rule, click Add Rule (+) in Deny Access Rules.

    2. To edit an existing rule, click Edit Rule.
      The rule settings dialog appears.

    3. In Rule Name enter a name for the rule and click Add.

    4. In Type select Device Risk Tier.
      In Operator appears is, that is no the default value for Device Posture risk tiers.

    5. In Value select High.

  6. Click Add Criteria (+).

    1. In Type enter the value, if applicable, or select the value for the access control type.

    2. Click Time to configure the time-based settings.

    3. In Start Time and End Time enter a time in hh:mm, AM-PM format.

    4. In time zone select a time zone.

    5. Select the days of the week that you want to deny access.

  7. Click Save.

  8. You can optionally configure Advanced settings. See Set up Advanced Settings

  9. Click Save and Deploy.

Add a tunnel-type client-access application

Add a tunnel-type client-access application to EAA Client and configure its parameters.

  1. Log in to Enterprise Center.

  2. In the Enterprise Center navigation menu, select Application Access > Applications > Applications.

  3. Click Add Application (+).

  4. In Type select Client-Access App. In Mode select Tunnel mode (multiple ports, UDP and TCP).

  5. Enter application name and optional description.

  6. Click Add Application.

  7. In App Settings > Settings configure the following:

    • Endpoint Host. Enter the external host of your application.
      This is the cloud endpoint for all communications between the client access application and Enterprise Application Access. Additionally, choose one of these domains:

    • Use your domain. If you use your own custom domain, you must provide a certificate configured as a complete bundle with all the subordinates (having the full chain of trust), otherwise you get a web-socket error.
      To use an uploaded certificate, select Use uploaded certificates and select the previously uploaded certificate.

    • Use Akamai domain. If you use an Akamai domain no certificate is needed.

    • Akamai Cloud Zone. The cloud zone should be a geographic location closest to the data center where your application resides.

  8. Optionally, you can add an application category for the app.

  9. Click Save.

  10. In Destinations > Settings you can configure different traffic types (TCP, UDP or both), different domains (wildcard or specific) or IP based access (with or without subnets), port ranges or specific ports or combinations of both.
    To add more destinations, click Add Destination and configure the next destination.

    πŸ“˜

    If a route for a particular destination already exists, then EAA Client does not add the IP address to the routing table, but will issue an IP route collision alert.

  11. To add connectors to the application select Connectors.

    πŸ“˜

    More than one connector is recommended for high-availability and load balancing.

  12. Click Associate connector and elect one or more connectors, and click Associate.
    To remove a connector, hover over it and click Disassociate.
    The associated connector appears in Connectors.

    πŸ“˜

    The connector should run to deploy the application.

  13. To add authentication to the application select Authentication.

    1. Enable Authentication.

    2. In Identity provider select an identity provider from the list.

    3. Click Assign Directory and select one or more directories from the list.

    4. Click Associate.
      The directory appears in Assigned Directories.

  14. To add an access control rule (ACL) to the application in Access enable Access.

    1. To create a new rule, click Add Rule (+) in Deny Access Rules.

    2. To edit an existing rule, click Edit Rule.
      The rule settings dialog appears.

    3. In Rule Name enter a name for the rule, and click Add.

    4. In Type select Device Risk Tier.
      In Operator is is now the default value for Device Posture risk tiers.

    5. In Value select High.

  15. Click Add Criteria (+).

    1. In Type enter the value, if applicable, or select the value for the access control type.

    2. Click Time configure the time-based settings.

    3. In Start Time and End Time enter a time in hh:mm, AM-PM format.

    4. In time zone select a time zone.

    5. Select the days of the week that you want to deny access.

  16. Click Save.

    πŸ“˜

    For a client access application, the Enable websocket support option is enabled by default. This option is required to establish a tunnel from the client to the EAA cloud.

  17. You can optionally configure Advanced settings, see Set up Advanced Settings

πŸ“˜

Note

If you're seeing performance issues for TCP applications in tunnel mode, click TCP Optimization, for higher throughput.

To provide selective access to some subdomains to some users, or certain IP addresses within the tenant see
Set up DNS exceptions and Add access control rules.

  1. Click Save and Deploy, to deploy the changes.

Limitations of tunnel-type 2.0 client-access applications.

Limitations of using multiple destinations with tunnel-type 2.0 client-access applications:

  • You cannot configure the same parameters for two destinations inside a tunnel-type client access application. For example, if you have Destination 1 and Destination 2 with the same parameters for traffic type, IP address host name, and same port you get a warning message.

  • You cannot configure two different tunnel-type client-access applications with the same destination parameters and be associated with the same identity provider. You get a warning message when you deploy the application.

Connect to TCP and UDP applications

Connect EAA Client to your TCP and UDP applications.

  1. Launch your TCP or UDP applications. If EAA Client is stuck in Connecting see Troubleshoot stuck in connecting state.

  2. Log out from your TCP or UDP application.


Did this page help you?