Create the application in Access Gateway
During this task we will create the web socket header application, which will host WebSocket policy.
- Sign in to the Access Gateway Admin UI console.
Click the Applications tab.
Click +Add to add a new application.
Select the Header Based option from the application menu, and click Create.
The New Protected Application wizard will start and display the Essentials pane for the application being added.
In the Essentials pane, specify the following:
Field Value Label A name for the application. For example header-websocket application. Public Domain A fully qualified host name. In this example www.mywebsocketapp.com. Protected Web Resource The URL of the protected resources.
In this example: backend.websocket.com.
Group Enter the group containing the users who should have access to the application. Description Optional. An appropriate description for your application.
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.
- Expand the Protected Web Resource tab.
- 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.
- Select a URL scheme. All added protected web resources will inherit this scheme. HTTP and HTTPS schemes are supported.
- Optional. Enable and specify Host Header value.
- Repeat as required:
- Click Add protected web resource. An empty row is added to the table.
- Enter a fully qualified hostname:port combination. For example, https://backendserver1.atko.com:7001.
- 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.
- Click Okay to add the new host.
- For existing hosts in the table, you can:
- Click edit () to modify an existing host.
- Click delete() to delete an existing host.
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.
- Enable Load Balancer Health Check.
- Click Edit to modify health check settings.
- Modify settings as required.
Path URI to resource used in health check. / Method HTTP method used. Always GET Status code HTTP status code used to determine health. 200 Interval Interval between health checks in seconds. 10 Request timeout Health check request timeout in seconds. 1 Healthy threshold Number of successful requests before a host is considered healthy. 3 Unhealthy threshold Number of failed requests before a host is considered unhealthy. 3
- Click Save to save changes or click Cancel to exit without saving.