1. Navigate to the web browser tab where you will reproduce the issue.
2. From the web browser's tools menu, open the developer tools menu item.
3. Choose the console log option.
4. Where available, choose the preserve or persist log option. This ensures that logging is saved across page reloads.
5. Reproduce the issue.
6. Save the log to send to RSA Customer Support.

Google Chrome (v64)

1. Open a new browser tab in Google Chrome.
2. Click on the three dot menu in the upper right corner of the Chrome window (it has a tooltip labeled Customize and control Google Chrome):  
3. Select More Tools > Developer Tools:

​

4. A new frame will open up in your Chrome tab, showing some markup language, and a menu at the top that looks like this:

5. Click on Console in the menu, to start the browser console for this tab.
6. Click on the blue cog icon  on the right of the browser console.  Some checkboxes will be displayed in the browser console as shown below:

 

7. Make sure that the options to both Preserve Log and Show Timestamps are checked.  Any displayed messages will now show timestamps, as shown below.

8. You are now ready to test. Reproduce the issue in the same Chrome tab where the browser console is running.  While you are testing, output will be logged by Chrome to the browser console.
9. When the test is complete, right-click any of the messages in browser console window, and choose Save as... from the displayed menu.

10. When prompted, specify a location to save the browser console log file.  Note the filename and location so you can send the file to RSA Support.

Mozilla Firefox (v58)

1. Open a new browser tab in Firefox.
2. Click to open the three bar menu in the upper right corner of the Firefox window (it has a tooltip labeled Open menu):  
3. Select  Web Developer > Web Console from the Firefox menu.   The browser console will be displayed:

4. Click the cog icon on the right of the browser console (it has a tooltip labeled Toolbox options):  
5. Scroll down to the Web Console section in the center of the browser console and tick the checkbox option for Enable timestamps.

6. Click the Console item on the browser console menu to return to the console view, then tick the Persist Logs checkbox on the far right of the menu.

7. You are now ready to test.  Reproduce the issue in the same Firefox tab where the browser console is running.  While you are testing, output will be logged by Firefox to the browser console.
8. When the test is complete, right-click any of the messages in browser console window, and choose Select All from the displayed menu.  This will highlight all the messages in the window.

9. Keeping all the messages highlighted, right click them and select Copy Message to copy all the messages to the Clipboard:

10. Paste the messages into a file using a text editor such as Notepad (Windows) or TextWrangler (macOS).
11. Save the file and note the folder and filename to send to RSA Customer Support.

• A browser console log may be requested by RSA Engineering to help diagnose problems shown by a web browser.
• By default, the browser console is cleared each time you navigate to a new page or reload the current page.  Normally Engineering will require the "persist" or "preserve" log option (depending on browser) to be checked to override that behavior (as advised in the instructions above)  Consequently Chrome or Firefox are preferred because they have that option.  Some versions of Microsoft Edge or Internet Explorer may not have this option.
• A browser console only captures data from the current tab.  If a web page opens a new tab or window, the data in the new tab or window will not be captured.
• A browser console log will typically be requested by Engineering in conjunction with a browser network trace.  A FiddlerCap capture is preferable to the browser's network trace option, as it will capture data from multiple tabs.  The instructions for FiddlerCap are browser-agnostic.  The end user can uninstall FiddlerCap at any time.