SAML troubleshooting: Capture an assertion

During a SAML sign-in, the browser, the service provider (SP, also known as Smartsheet), and the identity provider (IdP, this might be Okta, Azure, OneLogin, etc.) make several requests and responses to each other. One of those requests includes the assertion in which the IdP tells the SP information about the user logging in (509certificate, persistent ID aka IdP unique identifier, and email address aka Smartsheet unique identifier).

 What is an assertion?

An assertion is information passed from the IdP to Smartsheet or Resource Management. The assertion contains the authentication information Smartsheet needs to verify the right person is logging into the account. When users are having issues logging in or trouble setting up SAML, reviewing assertions can help troubleshoot what's wrong. 

In response to the assertion, Smartsheet will respond with, "Yes your certificate is valid and you have a valid persistent ID and email address, so you may log in." Or it may say, "No, your certificate is invalid (not secure) or you don't have the expected persistent ID or email address. Your login failed. This error might tell you what's broken."

These instructions tell you how to capture the assertion. Follow them carefully, save the file, and analyze the assertion using the guidelines in this article. 

To capture an assertion

  1. Close all incognito windows and then, open a new incognito window in Google Chrome. Select the upper-right Chrome menu > New Incognito Window to start with a fresh browser.
  2. Click the upper-right Chrome menu > More Tools > Developer Tools
  3. Open the Network tab and check the box for Preserve Log.
  4. Browse to: (or if troubleshooting Resource Management)
  5. Enter your email address in the box and click continue.
  6. If you're redirected to log in with your company credentials, go to step 7.
  7. If not, at the bottom of the screen a grey button labeled Your Company Account should appear. Click the Your Company Account button and log in with your company credentials.
  8. Provide your credentials to authenticate to your company's SSO system. This should reproduce the error.
  9. Select the Network tab at the top of the Developer Tools, and search for POST in the Filter field (or 'acs' for Resource Management).
  10. Select the POST result under Name (or 'acs' for Resource Management) and then select the Payload tab to the right. Scroll down and review the SAMLResponse in the Form Data section. This is an encoded assertion.
  11. Select all of the SAMLResponse, make sure to copy it in its entirety as it is a long section of text.
  12. Copy this encoded assertion, and browse to:
  13. Paste the encoded assertion message into the box under SAML Request, select the POST option below it, and click the decode button.
  14. Select XML View
  15. Save the file. You can now determine if there are errors or missing information. See Identify issues in a SAML assertion to learn what to look for.
Was this article helpful?