Whitelist Users and Request Types

Filter which requests are debugged by setting up whitelisting. If you don’t use whitelisting, all events in your org trigger debugging during a debugging session. Whitelist users or request types to focus only on the events that are relevant to the problem you’re debugging.

Force.com IDE is in a maintenance-only state. We still provide support for the product through our official channels, but updates prior to October 12, 2019 will be only for critical security issues that arise. On October 12, 2019, we will no longer provide support or updates of any kind for Force.com IDE. On that date, we will also begin archiving documentation and removing download links for the product. We recommend that you start migrating to Salesforce Extensions for Visual Studio Code or one of the great tools made by our partners. For more information, see The Future of Salesforce IDEs on the Salesforce Developers Blog.

Warning

  1. To access your debug configurations, select the arrow next to the debug icon (Debug icon), and then select Debug Configurations.
    Choose Debug Configurations from the debug icon's menu

    Typically, modifying an Eclipse debug configuration during a debugging session doesn’t affect active debug targets. However, whitelist modifications affect both current and future sessions.

  2. To set up whitelisting, select Whitelisting Enabled in your Remote Apex Debugger configuration.
    Remote Apex Debugger run configuration with whitelisting enabled
  3. To filter by user ID, enter a SOQL condition expression in the SELECT id FROM User WHERE field. Or enter a comma-separated list of user IDs in the text field in the User IDs section.
  4. To filter by request type, select one or more entry points, or enter a regular expression in the Entry Point Filter field. For example, to whitelist requests made by the Visualforce page myPage, enter .*/apex/myPage.apexp.