Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Identify and Trace a Specific Browser Requestor before a User Logs in to an Application

Troubleshooting | December 20, 2019 | 04:13

In this Global Client Support (GCS) video created by Rachit Agarwal, you will learn how to identify and trace a specific browser requestor before a user logs in to an application.

This approach can help in scenarios where multiple users report login issues where they are unable to log in to an application with some operator ID’s and they are unable to find the origin of the issue. In these cases, remote tracing helps identify the root cause of the issue.

Identify and Trace a Specific Browser Requestor before a User Logs Into an Application

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us