Single Sign On With SAML


This guide assumes that you already have a SAML Identity Provider up and running.


Configuring SAML (Security Assertion Markup Language) for your Datadog account will let you and all your teammates log in to Datadog using the credentials stored in your organization’s Active Directory, LDAP, or other identity store that has been configured with a SAML Identity Provider.

Configure SAML

If you are a Datadog Admin, there is a “Configure SAML” option in the drop down menu that is accessed by clicking on your username in the upper right corner of the Datadog web page.

That brings you to the “SAML Single Sign On Configuration” page where you can:

  1. Upload the IdP Metadata from your SAML Identity provider by clicking the “Choose File” button.

    After you’ve chosen the file, click “Upload File”.

  2. Datadog’s Service Provider metadata can be found here. You can use this SP Metadata to configure your IdP to recognize Datadog as a Service Provider.

  3. After you upload the IdP Metadata and configure your IdP, you will need up enable SAML in Datadog by clicking the Enable button.

    Once SAML is configured in Datadog and your IdP is set up to accept requests from Datadog, users can log in by using the Single Sign On URL that is shown in the Status box at the top of the SAML Configuration page.
    The Single Sign On URL will also be displayed on the Team page. Loading this URL will initiate a SAML authentication against your IdP. Please note that the URL will not be displayed until SAML is enabled for your account.

Datadog Service Provider Details

  • Datadog supports the HTTP-POST binding for SAML2: urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST.
  • Datadog will specify urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress for the Format of the NameIDPolicy in Assertion Requests.
  • Assertions must be signed.
  • Assertions can be encrypted, but unencrypted assertions will be accepted.
  • Datadog’s SP Metadata can be found at

Setting Attributes

  • Attributes may be included with the Assertion. Datadog looks for 3 Attributes in the AttributeStatement:
  • eduPersonPrincipalName: If specified, the eduPersonPrincipalName must correspond to the user’s Datadog username. The username is usually the user’s email address.
  • sn: This is optional, and should be set to the user’s surname.
  • givenName: This is optional, and should be set to the user’s first, or given name.
  • Datadog expects that Attributes use the NameFormat urn:oasis:names:tc:SAML:2.0:attrname-format:uri or urn:oasis:names:tc:SAML:2.0:attrname-format:basic. The name used for each attribute will depend on the NameFormat that your IdP uses.
  • If your IdP is configured to use the NameFormat urn:oasis:names:tc:SAML:2.0:attrname-format:uri:
  • eduPersonPrincipalName: The IdP should set urn:oid: as the Name of the Attribute
  • sn: The IdP should set urn:oid: as the Name of the Attribute
  • givenName: The IdP should set urn:oid: as the Name of the Attribute
  • If your IdP is configured to use the NameFormat urn:oasis:names:tc:SAML:2.0:attrname-format:basic:
  • eduPersonPrincipalName: The IdP should set urn:mace:dir:attribute-def:eduPersonPrincipalName as the Name of the Attribute
  • sn: The IdP should set urn:mace:dir:attribute-def:sn as the Name of the Attribute
  • givenName: The IdP should set urn:mace:dir:attribute-def:givenName as the Name of the Attribute
  • If eduPersonPrincipalName exists in the AttributeStatement, the value of this attribute will be used for the username. If eduPersonPrincipalName is not included in the AttributeStatement, the username will be taken from the NameID in the Subject. The NameID must use the Format urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.
  • If sn and givenName are provided, they will be used to update the user’s name in their Datadog profile.

Specific SAML IdP

For more information about configuring specific IdP’s, refer to the following Knowledge Base articles:

Additional Features

The following features can be enabled through the SAML Configuration dialog.

Just-in-Time (JIT) Provisioning

With Just-in-Time provisioning, a user will be created within Datadog on the fly the first time they try to log in. This eliminates the need for admins to manually create user accounts one at a time.

Some organizations might not want to invite all of their users to Datadog. If you would like to make changes to how SAML works for your account, please contact support. It is up to the organization to configure their IdP to not send assertions to Datadog if they don’t want a particular user to access Datadog.

Admins in accounts using SAML can also set the default role for new Just-in-Time users. The default role is currently Standard, but you can choose to add new JIT users as Read-Only or even Admin.

IdP Initiated Login

The normal workflow is that when the Datadog url is loaded, the browser is redirected to the customer IdP, user types in credentials, then the IdP redirects back to Datadog. Some IdPs have the ability to send an assertion directly to Datadog without first getting an AuthnRequest (IdP Initiated Login).

In the normal setup, we won’t know which org the assertion came from and this will result in an error page with a message saying that SAML Response is missing “InResponseTo” attribute.

After enabling the feature (and waiting for caches to clear) the customer will need to get a new version of the SP Metadata, which will have a different, org-specific AssertionConsumerService endpoint to send assertions to.