How To: Create a SAML Trace

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All

     

    Overview

    This article explains how to install SAML-tracer and capture a SAML trace. When implementing SAML applications, the SecureAuth Support Team may ask for a SAML trace to debug the issue.

     

    Create a SAML Trace

    1. Install the SAML-tracer add-on to your web browser. MS Edge Chromium and Google Chrome users can install it from the Chrome Web Store: go to https://chromewebstore.google.com, search for "SAML tracer", and click the SAML-tracer result.

      The Chrome Web Store search results for 'saml tracer', showing the SAML-tracer extension with a 4.4-star rating.
       
    2. Click Install to add the extension to your browser.
    3. Once installed, launch it from the browser's Extensions menu.

      The Edge browser's main menu with Extensions highlighted.
       
    4. Click SAML-tracer in the Extensions menu to open it.
      The SAML-tracer entry in the browser's Extensions menu.
       
    5. While SAML-tracer is open, launch and log in to the SAML application having issues.
    6. Reproduce the issue, then in SAML-tracer, click Export
    7. Ensure None is selected for Select cookie-filter profile:, click Export to download and save the SAML trace to your local machine.
    8. Upload or email the downloaded SAML trace to the SecureAuth Support Team for review.

     


     

    Special Considerations

    If multiple browser tabs are open, SAML-tracer may capture information from every SAML-enabled application currently running. For a clean trace of only the application you're debugging, keep a single browser window open with SAML-tracer while you reproduce the issue.


     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.