Applications Systems
How to handle browser-level authentication in WPM recordings
To authenticate a user in recordings created in the new WPM Recorder, WPM reads the User Name and Password from the URL but does not send it to the Orion Server for authentication. This means that client certificates cannot be checked and it's possible that users may see the password provided in an unencrypted format.
First published date
6/6/2019 1:55 PM
Last published date
12/2/2019 8:36 PM
Overview
To authenticate a user in a recording created in the new WPM Recorder introduced in WPM 3.0, WPM reads the User Name and Password from the URL but does not send it to the Orion Server for authentication. Client certificates cannot be checked and users may see the password provided in an unencrypted format.
Product section
Web Performance Monitor
Resolution
Follow these recommendations for recordings that include authentication:
- An authentication step can occur anywhere in a recording sequence, but should always occur as the first step on any page that requires it. For example, if one page doesn't require authentication but the next page does, logging in should be the first step on the second page.
- Use an explicit navigation action to open the secured page, enter valid credentials, and click the button (perhaps named Sign in, Login, or Submit) to finish the sequence.