Create no-auth application in Access Gateway

During this task we will create the no-auth application.

Create the application

  1. Sign in to the Access Gateway Admin UI console.
  2. Click the Applications tab.

  3. Click +Add to add a new application.

  4. Select the No-auth option from the application menu, and click Create.

    The New Protected Application wizard will start and display the Setting tab for the application being added.

Configure the no-auth application settings

  1. The Settings page provides options to configure the application. Review the options and make the appropriate changes.
    SeeAbout application settingsfor more information on the application settings options.
  2. Enter the following values in their respective fields, and click Next.
    FieldValue
    Public Domainnoauth.okta.com
    Protected Web Resource https://header.service.gateway.
    See also Configure load balancing.
    Post Login URL https://noauth.okta.com
    Groups Select the IDP group that can access this application.

Configure load balancing

Available since Access Gateway version 2022.2.3

Okta recommends that whenever possible load balancers and Access Gateway as a load balancer be implemented.
See About Access Gateway load balancing.

  1. Expand the Protected Web Resource tab.
  2. Enable Load Balancing By Access Gateway.

    The Protected Web Resource tab expands to include a table of hostnames and weights that represent the target load balancing instances. This table is initially empty.

  3. Select a URL scheme. All added protected web resources will inherit this scheme. HTTP and HTTPS schemes are supported.
  4. Optional. Enable and specify Host Header value.
  5. Repeat as required:
    1. Click Add protected web resource. An empty row is added to the table.
    2. Enter a fully qualified hostname:port combination. For example, https://backendserver1.atko.com:7001.
    3. Enter a weight between 1 and 100. Enter 0 to specify a disabled host.

      Weights represent the percentage of requests that will be routed to this host.

      For example, two hosts of weights 2:1 would result in requests being routed ~66% to the host weighted 2 and ~33% to the host weighted 1.

    4. Click Okay to add the new host.
  6. For existing hosts in the table, you can:
    • Click edit () to modify an existing host.
    • Click delete() to delete an existing host.
  7. Optional. Configure health checks:

    Health checks use GET operations to confirm that back end resources are functional.

    New requests aren't routed to resources that have been labeled unhealthy by the health checks.

    1. Enable Load Balancer Health Check.
    2. Click Edit to modify health check settings.
    3. Modify settings as required.
      FieldValue

      Default

      PathURI to resource used in health check./
      MethodHTTP method used.Always GET
      Status codeHTTP status code used to determine health.200
      IntervalInterval between health checks in seconds.10
      Request timeoutHealth check request timeout in seconds.1
      Healthy thresholdNumber of successful requests before a host is considered healthy.3
      Unhealthy thresholdNumber of failed requests before a host is considered unhealthy.3
    4. Click Save to save changes or click Cancel to exit without saving.