The HTTP web session (VNCHTTP) takes place in an isolated environment containing an optimized and protected browser to access websites. User interactivity is similar to the RDP session.
The browser is configured to prevent opening new tabs. All graphical components of the browser are hidden. Even the interaction menus and hotkeys are locked.
It is possible to make the browser interface more flexible by enabling the use of tabs or the full interface. However, the behavior varies between Firefox and Chromium browsers. More information about commands and limitations can be found in Command for partial release of browser tabs in VNCHTTP sessions.
To access a website, a complementary procedure is required in relation to that required for other devices, which normally only needs connectivity and an access credential.
Websites require authentication configuration. This configuration allows our embedded browser to automate login steps.
During this authentication process, the user will be presented with a protective banner that prevents the user from interfering and seeing the authentication in progress. Your interactivity will be returned only when the login process ends with success or failure.
- Modern websites have confirmation steps using Captcha and MFA Tokens to prevent automated systems from carrying out unwanted access. In these cases, the Web Proxy returns interactivity for the user to continue the authentication step.
- The MFA Token can be used automatically. Configure the tag (
token_totp) in the web session parameterization to do this. More information in About Customize settings - Web sessions parameters and How to register a new web session parameter.