Containerization of Web Browser

in order to be able to record videos of the http sessions, the http session must be initiated with a different method than the one outlined previously to enable the containerization feature, the corresponding licenses are required in this section, we only address the required configurations more details about the containerization feature can be found in our user manual how to reach http devices through containers to set the resources for the containers to be created navigate to administration > system config man set the resources of containers parameter with one of these values local, remote, or all these values define which kind of resources will be used by the container manager to define which user(/s) should reach http devices through containers navigate to user accounts > user group definition > device group properties set the accessovercontainer property key as true to specify which http device access to use containerization navigate to device inventory > device properties set the accessovercontainer value as true after saving this setting couple, some of the additional properties will be loaded automatically those automatically set property keys can be found on the below screen below the http proxy ca certificate and kron extension need to be installed after reaching the container for the first time then the browser profile needs to be copied to the container volume to be used by newly created containers in the future there is no need for proxy settings on the browser the process is the same for as is http proxy use through a native browser to copy the ca certificate from the pam instance to the shared volume and complete the initial setup open the containerized browser through the pam management ui or desktop client open an ssh session to the pam instance get the running container id from the session window that opened on the first step $ docker ps format {{ id}} use the docker id to copy the ca certificate to the container $ docker cp /u01/http proxy/assets/ca crt /home/ubuntu/desktop the ca certificate can be found on the desktop and it needs to be added and trusted by the browser the same procedure needs to be followed for http proxy native web browser usage to install the firefox extension the same procedure should be used for native browser usage it would be useful to pin the extension onto the toolbar activate the extension and close the firefox app to copy current settings to the shared volume it is important to close the firefox app, otherwise, open tabs will be prompted at every single container run the command below on the container’s terminal mkdir p /shared volume/mozilla/firefox orig && cp a / mozilla/firefox/ default release /shared volume/mozilla/firefox orig && cp a / mozilla/firefox/profiles ini /shared volume/mozilla/firefox orig this step needs to be completed only once before end users start using containers daily from now on, that http device can be reached only from the pam management ui and desktop client app by the defined individual accounts