When troubleshooting Security Assertion Markup Language (SAML) or working with Okta Support, it may be necessary to capture browser traffic for investigation. This can be done using built-in browser tools, such as Chrome’s Developer Tools. This article describes how to capture traffic when it involves multiple tabs.
- Secure Assertion Markup Language (SAML)
- Browser Tools
Often SAML login flows will involve multiple tabs. For example, when logging in to an application from the Okta Dashboard, upon clicking the application tile (IdP Flow) a new tab opens where the login traffic will occur.
Browser Developer Tools will only capture traffic on one tab, so when a new tab is opened automatically as part of the login process, this traffic may not be captured.
Users can work around this limitation by manually opening a new tab, enabling network traffic collection in-browser tools, and pasting the desired URL in the new tab. This will ensure the login flow is captured within the tab where DevTools is open.
- For example, capture the login flow by clicking an application tile in Okta Dashboard, right-clicking the tile, and selecting copy link address. Then, paste this in the new tab with DevTools open and recording network traffic. This will ensure the flow is captured.
For an automated option or scenarios involving multiple tabs, also enable the browser tools to open when tabs are opened automatically. Enable the feature described below, then perform the steps to perform .har collection, and the browser will automatically open new DevTools for any tabs that pop up. If capturing logs for Support, make sure to export the .har file from all tabs where the relevant traffic occurred.
For Chrome
This problem can be overcome by enabling the “Auto-open DevTools for Popups” in DevTools Settings. This will enable Chrome to open a new DevTools instance for each new tab opened automatically during the login flow.
- DevTools Settings > Preferences > Global > enable Auto-open DevTools for popups
