This section will show you how to make an HTTP service available through Border0 using your single sign-on credentials.
- Create an HTTP socket and link it to your Border0 connector
- Authenticate and Connect
- Kill the session and watch the recording
We'll start by creating a socket in the Border0 portal.
- In the Sockets page, click on new HTTP socket
- set a name and optionally a description
For HTTP Sockets we can set the following upstream parameters
- upstream protocol, either http or https. In our example we'll select
- provide the hostname, in our case we'll select
- Optionally we can also set the upstream HOST / SNI field, this is important if the origin is expecting a specifc host header. We'll set it to
The last step is to link the connector you wish to use for this new socket: select your connector from the list
Internal web applications
In this example we're using www.example.com , however you can use any http endpoint, including private internal web applications. As long as the connector has access to the web app, you'll be able to make any http(s) service available. For example https://10.10.10.10
Once you're new socket has been created, the status indicator should show "alive". This indicates the connector has picked up the configuration and is ready to serve traffic for your new socket.
now visit the url of your new http socket, or simply click on the blue connect button to visit your new http socket. You'll be asked to authenticate. Access is controlled by the policies attached to your socket.
The video below demonstrates the process.
Note that the default organization-wide policies will be applied. Visit the Policy tab in the socket details page to modify the policy settings for this service.
Optionally, session recording for HTTP sessions can be enabled in the portal, as can be seen in the image below.
After that, you can see session recordings in the sessions tab of this socket. An HTTP session recording will show you the rendering of the HTTP DOM data. And can be replayed as a movie in the Border0 portal. See below for an example.
For your internal web app, it is helpful to know what user (who) is making the HTTP requests. The Border0 Identity aware proxy makes that information available to your internal Application by adding the following extra HTTP headers to the upstream request. In other words, your private application will have access to the following HTTP headers.
"X-Auth-Email": "[email protected]",
"X-Auth-Name": "John Doe",
"X-Auth-Userid": "[email protected]",
"X-Auth-Username": "[email protected]"
Updated 3 months ago