Configure access parameters for an application

How to manage access to your applications.

Configure access parameters such as the server’s private IP address or fully qualified domain name, whether your server runs HTTPS or HTTP, add external domain certificate, origin server certificate for HTTPS traffic, and the nearest cloud zone for an application. For more information on specific application types, see Configure and deploy a remote desktop (RDP) application and Configure and deploy a SSH application. To create a new application see Add an application to EAA.

How to

  1. Log in to the Enterprise Application Access (EAA) Management Portal.
  2. From the top menu bar, click Applications. The application cards appear.
  3. Click the application card for the application you want to configure.
    The application information appears.
  4. Click Settings > GENERAL.
  5. The Application Server IP/FQDN type is prepopulated based on the Application Profile. In the first Application Server IP/FQDN field select one of these:
    • HTTPS Section:

      https .(default) Select this option for secure web traffic.

      Verify Origin Server Certificate. (on-by-default) Allows you to do the origin server certificate validation. (recommended). Also select a root CA certificate.

      ROOT CA Certificate. Choose the root CA certificate with the full bundle you uploaded into EAA. See Upload a ROOT CA certificate for origin server validation.

      Note: If you choose https, but disable Verify Origin Server Certificate, you will see a warning message:

      Note: If you enable Verify Origin Server Certificate and do not upload a ROOT CA Certificate, you see a warning message:

    • HTTP section:

      http. Select this option if you want http traffic.

  6. In the second Application Server IP/FQDN field, enter either a valid internal IP address for the server or the fully qualified domain name (FQDN) that you use to access this server when inside your company’s network.
  7. In the third Application Server IP/FQDN field, enter an IP port number.
    Note: For HTTPS, IP port 443 is default. If your application doesn’t normally redirect you to the login page, you may need to include a suffix (for example, /login) in the third field.
  8. To configure multiple applications servers for load balancing, click Add More. EAA supports various load balancing techniques including round-robin, session or cookie stickiness, and source IP hash.
  9. If you are configuring a VNC application, optionally enter a VNC passphrase or password, if your server is configured to allow access via VNC.
  10. Select a External Host Name domain type, then enter an external host name for the application.
  11. Select the Akamai Cloud Zone located closest to the data center where your application server resides.
  12. Associate a connector with the application. Click Add/Remove connector and select a connector to associate with the application, such as the VMware connector.
  13. Click Done.
  14. To add more connectors, click Add/Remove connector.
    Note: EAA recommends more than one connector for high-availability and load balancing.
  15. Click Save and go to Authentication.
    The Authentication tab opens.
  16. Configure authentication,
  17. Click Save and go to Services.
    The Service tab opens. If you want to configure these optional services, see Set up services for an application.
  18. Click Save and go to Advanced Settings.
    The Advanced Settings tab opens. If you want to configure these optional advanced settings, see Set up advanced settings for an application.
    • If you are using SAML as the Application-facing authentication mechanism, click Save & Go To SAML Settings. For more information, see EAA as the SAML identity provider.
  19. Click Save and go to deployment. The deployment tab opens.
  20. If all required information for the application is configured, the application is ready for deployment. Click Deploy Application. To learn more see Deploy the application.

What you should see

The deployment takes between three to five minutes. When deployed, your application is ready for secure access by your users.