Configure single sign-on for Azure AD

Before you can configure single sign-on (SSO) for Azure AD in Incident Response you need to obtain the right credentials.

Before you begin

Note: While this integration with a third-party product is supported, the documentation here is based upon information provided by that third-party. More current information about the operation of that third-party’s system may be available from them directly.

Role required: admin


  1. Sign in to Azure portal.
  2. In the left pane, select the Azure Active Directory service.
  3. Go to Enterprise Applications.
  4. Select All Applications.
    If an application already exists for our Lightstep Incident Response account, click on that application and skip to Step 8.
  5. To add a new application, select New application.
  6. In the Browse Azure AD Gallery page click on Create your own application.
  7. On the Create application page, provide a descriptive name for your application.
  8. Select the What are you looking to do with your application? > Integrate any other applications you dont' find in the gallery (Non-gallery) option.
  9. Click Create.
    The application is created.
  10. Go to the Application Integration page.
  11. Find the Manage section.
  12. Select Single sign-on.
  13. On the Select a single sign-on method page, select SAML.
  14. On the Setup Single Sign-On with SAML page, select the icon for Basic SAML Configuration section.
  15. In the Basic SAML Configuration section:
    1. Under Identifier (EntryID) click on Add identifier.
    2. In the text box, enter the URL for our Lightstep Incident Response account. (https://<your subdomain>
    3. Click Save.
  16. In the SAML Signing Certificate section, download Certificate (Base64).
  17. Make a note of your Azure AD Identifier and Login URL.
  18. Logout.
  19. Log in to Incident Response.
  20. On the navigation pane, select Admin.
  21. On the Single Sign-on, OAuth Identity form, select Set up and manage SSO.
    Note: Only one authentication feature can be enabled at a time.
  22. Select Edit.
  23. Fill in the SSO fields.
    Field Description
    IdP Issuer URI/Entity ID Issuer URI of the Identity Provider. This value is usually the SAML Metadata EntityID of the IdP EntityDescriptor.
    IdP Login URL The binding-specific IDP Authentication Request Protocol endpoint that receives SAML AuthnRequest messages from Incident Response.
    IdP Logout URL [Hidden] Visible when Single Sign Out is enabled. This is the logout endpoint for IdP.
    IdP Signature Certificate
    The PEM encoded public key certificate of the Identity Provider used to verify SAML message and assertion signatures.
    Note: Wrap this field with ––-BEGIN CERTIFICATE----- and ––-END CERTIFICATE----- text.

    A certificate expiration date is generated after successfully adding the certificate. Placeholder alt text for cert-expiration-date

  24. Optional: To activate single sign out, select the Enable Single Sign Out toggle switch.
    When enabled it completes the user IdP logout. Otherwise, their logout is only from Incident Response.
  25. Select Save.
    Figure 1. Okta SSO configuration form example
    Completed SSO configuration form
  26. Use the Test connection button to make sure your configuration works.

    Test connection creates a popup with your results.

    When the test succeeds, you can select Activate to enable SSO.

    If the test failed, follow the instructions in the popup and select Close to continue editing.

    Once you have successfully tested your configuration and activated, you're done. Your SSO configuration is enabled.
    Note: To disable the configuration, use the Enable Single Sign In toggle switch back to the off position.

    See Configure OAuth identity authentication for detailed information on configuring and managing OAuth authentication.

What to do next

See Sign in to Incident Response using Single Sign-on, OAuth, or multi-factor authentication.