Add WebSocket based application
HTTP and WebSocket both are communication protocols used in client-server communication. HTTP is unidirectional where the client sends the request and a server responds. WebSockets, on the other hand, is bidirectional and a full-duplex protocol that is used between the client and server.
Access Gateway supports WebSocket based applications by adding a policy directives to those URIs associated with WebSocket end points. The following pages describe the tasks required to define a header based application and then create policy for each web socket based URI.
Before you begin
Ensure you have available:
- An appropriate DNS entries for both the web socket application and the external exposed new URL exist.
For example:Value Description https://external.domain.com External application. The URL clients use https://internal.domain.com Protected application URL. - A list of any required application header attributes exists along with their expected content.
- A list of all Web Socket based URIs exist, so that each can be tagged as a web sockets using policy directives.
Typical workflow

Note
All tasks in this workflow are typically handed by the Access Gateway administrator.
Task |
Description |
---|---|
Create a containing group |
|
Create header application |
|
Assign Certificate |
|
Add additional attributes |
|
Add required access policy |
|
Test the application |
|
Troubleshoot |
|