L7 firewall configuration
L7 Firewall configuration. This guide provides helpful information if you need to secure your Cobrowse implementation behind a L7 firewall.
Last updated
Was this helpful?
L7 Firewall configuration. This guide provides helpful information if you need to secure your Cobrowse implementation behind a L7 firewall.
Last updated
Was this helpful?
This guide contains some information that can be useful when needing to secure your implementation behind a L7 firewall. There are two subsets of the API that are generally used by internal vs external roles.
Here you can find the subset of the APIs that must be accessible to end user devices running our SDKs.
If you choose to using the version that is shipped with your deployment, then you will also need to add that route.
These are the APIs required by the agent dashboard, or embedded agent side UI.
As well as the routes above, the HTML frontend must also be accessible for agents. Paths include.
Important: The frontend is built as a static single page application, with an index.html entrypoint. Any route not included in the prefixes listed above should be considered a frontend route and resolve to /index.html.
All headers, including custom headers, must be forwarded on the non-frontend routes. All query parameters must be forwarded on all routes.
Warning: We may add routes and parameters between versions. We always recommend deploying new software versions to a staging environment and testing behind your firewall configuration before promoting new versions to production.