The installation of browser extensions may not be always possible for the user, which means sites that require the AVG Browser Extension cannot be used in some cases. It is however possible to configure some sites using a Custom User-Password app instead.
The compatibility of the Custom User-Password app is completely dependent on the login implementation of the target site itself. This app can only be used with login pages which do not require cookies or header information to be passed.
Note: The Centrify Browser Extension logs the user in by loading the login page first, and then automatically filling in the credentials for them. This means that to the webpage, this is no different than if the user entered the credentials themselves. The Custom User-Password app is different as it bypasses the login page and submits the form information directly to the login request URL. This method will not work for all login pages, for example with some sites that require dynamic information to be submitted with the login attempt (such as timestamps, session IDs, etc). For login pages that only require static variables, the Generic User-Password app can usually be used to login. The capture tools shown in this KB require a recent version of Chrome or Firefox installed.
Steps to capture login variables:
response.AddFormField("email", encode(LoginUsername)); response.AddFormField("password", encode(LoginPassword));Some login pages will send additional info with the username and password.
For example if the form data is captured as:
Then the script will look like this:
response.AddFormField("login-user", encode(LoginUsername)); response.AddFormField("login-pass", encode(LoginPassword)); response.AddFormField("action", "[Submit]"); response.AddFormField("option-selection", "4"); response.AddFormField("option-keepme", "true");
Note: Notice the user's actual username and password are NOT saved in the script, these are saved on a per-user basis and will be automatically substituted into the request via the encode(LoginUsername) and encode(LoginPassword) parameters. Configure the rest of the app options as needed and then save and deploy the app. When the users click on the custom app for the first time, they will be prompted for their credentials for the target site. Once the credentials are saved, they will submitted directly to the login page without the need for the AVG Browser Extension. For further information and additional scripting options, see the User-Password Scripting Guide in the AVG Cloud Service Online Help.