I’m building a test case for automated logins on a closed server environment. Because one of the applications has a non-webpage login interface (see screenshot below), I have to use the Authenticate command instead of targeting the username and password fields.
The problem is, the closed environment has a strict proxy access policy, where all application pages, such as the one shown above, have to be accessed through a link portal page. If you try to access the site directly using the URL or a bookmark, the proxy will automatically redirect the user to a warning banner, and then to the link portal. This interrupts the Authenticate command, which uses URL navigation.
Is there a workaround for this?