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 from the 3 3 1 release on, the initial manual operation to set up containers will no longer be needed thus, the steps outlined in the how to reach http devices through containers release 3 3 1 document should be followed before continuing the configuration, the base image can be installed by the support team or can be downloaded via the following command on the pam instance cli docker pull krontechnology/containerization 331 then its name should be changed with the following command $ docker image tag krontechnology/containerization \<relevant current tag> http proxy image to check that the operation was successfully executed use the command $ docker image ls 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 > user 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 screen below from now on, that http device can be reached only from the pam management ui and desktop client app by the defined individual accounts