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.
Ensure you have available:
- An appropriate DNS entries for both the web socket application and the external exposed new URL exist.
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.
All tasks in this workflow are typically handed by the Access Gateway administrator.
|Create a containing group||
|Create header application||
|Add additional attributes||
|Add required access policy||
|Test the application||
- See Access Gateway supported application and version information for details of supported application and version information.
- See Add a generic header application.
- See Add a sample policy application.
- See Troubleshoot applications.
- Add or review application essential settings. See About application essentials and Manage application essentials.
- Add application behaviors. See About application behaviors.
- Add fine grained policy to further protect resources. See About application policy and Manage access control application policy for an overview on user policy and for examples respectively.
- Extend existing policy using custom configuration. See Advanced Access Gateway policy.