Sites behind HTTP basic auth used to get stopped on every Trainer replay with the browser's own authentication prompt, so you had to retype the same username and password on each launch. Starting with mabl Desktop App version 2.67.2, the Trainer applies a saved basic auth credential when it opens the browser. Tests you create on a plan inherit that plan's basic auth credential automatically, and you can select a credential yourself when you create a browser test or launch the Trainer.
The credential follows the rest of your work in the Trainer, too. Run test locally and Run test in cloud in the play menu both use it, and the mabl agent applies it when it builds a browser test in the cloud.
Try it out
If your test belongs to a plan that has HTTP basic auth configured, no action is required. Launch the Trainer from that test and the plan's credential is applied for you.
To choose a credential for a test that isn't part of a plan:
- Create a new browser test, or open an existing one and launch the Trainer.
- Under Optional configurations, find the Authentication section.
- Select a credential from the HTTP basic auth credentials dropdown.
- Launch the Trainer.
When the mabl agent plans a cloud build, you can set the same credential from the test information panel sidebar before the agent starts authoring.
A few limits worth knowing:
- The credential is applied when the browser launches. It cannot be updated partway through a training session.
- Basic auth credentials apply to browser tests only. API tests have their own auth settings, and mobile tests are unaffected.
- Cloud credentials can't be used for local training, because their secrets aren't retrievable outside the mabl cloud. They do work when the mabl agent builds a test in the cloud.