I have an environment setup where the development team have provided access with 3 steps:
- Enter Browser: URL for Form based Authentification.
- Login using 1 from options of 100 test ID's
- Enter Browser: URL for application (this still has SSO)
In the raw browser: Chrome / IE11, a user can follow the 3 steps and reach the application as the TEST ID user.
When trying the same in TruClient with Chromium the application is always loaded with the SSO ID.
My Question / Request for Help is............Is there any way of LoadRunner managing this conflict the same way that the raw browser does??