Dynatrace SaaS enables authentication through your organization's identity provider (IdP). If you want to use your organization's corporate credentials for authentication in Dynatrace, you can set up SAML to delegate authentication to your IdP.
SAML 2.0 is used for authentication. Based on the domain part of your corporate email address, Dynatrace can determine if SAML was configured for that domain and redirect to your company’s IdP for authentication.
Your IdP needs to follow some basic SAML specification and security requirements to be compliant with Dynatrace SSO:
- The entire SAML message must be signed (signing only SAML Assertions is insufficient and will generate a
400 Bad Requestresponse)
- The SAML protocol version is
- IdP response
NotOnOrAfterassertion timestamps must consider system clock skew and must be set to at least 1 minute before and 1 minute after the current time (this particularly concerns AD FS default settings)
- The IdP response status code must be
- No assertion encryption
If your IdP already has an application that uses the previous Dynatrace SSO model (
https://signin.dynatrace.com), you'll need to create a new application. Keep the old configuration enabled until the new configuration is tested and verified and all of your users have been successfully transitioned.
Dynatrace SSO SP metadata is provided at https://sso.dynatrace.com/sso/metadata. If your IdP requires manual configuration and you don't have any XML parser addons installed in your Chrome browser, we recommend that you view the metadata in Firefox.
Depending on the IdP type, these endpoints need to be configured as follows:
https://sso.dynatrace.com:443/saml2/loginfor Entity ID / Audience Restriction
https://sso.dynatrace.com:443/saml2/sp/consumerfor Single Sign On URL / Destination URL / Recipient URL
https://sso.dynatrace.com:443/saml2/sp/logoutfor Single Logout Service URL
If your IdP configuration screen contains the option to set SAML bindings for login or logout, set it to
SAML federated IdP configuration
To set up SAML for your domain
- Go to account settings in the user menu and select Single sign-on from the entries on the left.
- Create a fallback user account
- Verify your ownership of the domain
- Configure metadata
- Test your configuration
1. Create a fallback user account
When a user signs in, Dynatrace checks the domain part of your corporate email address to determine whether SAML was configured for that domain. If there is a match, the sign-in is redirected to your company’s IdP for authentication. For a fallback, you need an email address that will not be redirected like this.
You need to create a fallback user account so you don't get locked out if you have configuration troubles.
Your fallback account must be a non-federated user account that has the manage users and manage groups permissions and isn't covered by the federated login.
- Invite a user with a non-federated email address (an email address with a different domain than the one for which you are setting up SAML).
- Specify the manage users and manage groups permissions in the invitation (users can be invited via the User management page).
2. Verify your ownership of the domain
Before you can configure the domain for which you want to set up SAML, you need to prove ownership of the domain.
- Select Single sign-on from the menu on the left and then select Add new domain to begin specifying a domain.
- In the Domain box, enter the domain (for example,
@mycompanyname.com) for which you want set up SAML.
- Select Copy and add the TXT resource record to your domain’s DNS configuration.
- Select Verify so that Dynatrace can verify that the record was added to your domain’s DNS.
It may take a few minutes for the record to be propagated in the DNS system and the value to become available for Dynatrace to verify.
- After successful verification, the Verify button changes to Verified as in the example.
3. Configure metadata
Select Add configuration to start configuring metadata.
Select Download XML to download the service provider (SP) metadata displayed in the Service provider SAML 2.0 XML metadata.
- Alternative: if you prefer, you can select and copy the displayed data from this page instead of downloading a file.
Register the data at your IdP and get the metadata of your IdP in XML format. The activities involved in this step depend upon your IdP's interface and requirements.
Select Upload XML to upload the file containing the metadata of your IdP in XML format.
- Alternative: if you prefer, you can paste the IdP metadata text directly into the Identity provider SAML 2.0 XML metadata box instead of uploading a file.
In the Attribute mapping section, specify the following:
- First name attribute is the attribute that contains the first name of a user.
For Microsoft Azure, it's
- Last name attribute is the attribute that contains the last name.
For Microsoft Azure, it's
- Security group claim attribute contains the groups/roles of a user from your IdP. This field is needed if you want to use SAML authorization.
- First name attribute is the attribute that contains the first name of a user.
Select Validate configuration to verify your settings. You may need to log in to your SSO.
If validation is successful, Dynatrace will display a confirmation message:
Close that message to return to the Add configuration page and then select Continue to display a summary of the validated configuration.
Select Single sign-on to enable your configuration.
Note: Don't log out of Dynatrace yet in case any SSO issues occur.
Select Save to save your configuration.
4. Test your configuration
To test your configuration
- Open a new browser instance and a new incognito window.
- Navigate to sso.dynatrace.com and enter your email address at the login page.
- Select Next.
You should be redirected to your company’s IdP.
- Provide your domain password.
After successful authentication, you should redirected to your Dynatrace environment’s home page.
If you experience trouble, use the non-federated user (the fallback user account you created earlier) to change the configuration or disable federation. See Frequently asked questions below for assistance with technical issues.
You can use SAML authorization to manage permissions in Dynatrace. To do so, you need to map groups from your IdP to groups in Dynatrace.
Select Group management and select a group.
- We strongly recommend that you create a new group first (select Create new group) to test whether SAML authorization works for that group.
- Make sure that you have a non-federated user with manage groups permission as discussed earlier.
When you specify a Security group claim name for a group and select Save
- All existing users from that group will be removed
- The group becomes a federated group. Assignment of users to that group is then controlled via the Security group claim attribute that you specified on the Single-sign on page.
Expand the Edit pane of a group to set up the mapping.
Specify a value in the field Security group claim name. This is the federated group name that is returned by your IdP and that this Dynatrace group is mapped to.
- This typically isn't a group display name. It may be, for example, an LDAP ID.
SAML federated group mapping - example
Note: Don't log out of Dynatrace yet.
Open a new browser instance and a new incognito window and perform the login.
Navigate to account settings (select Account settings in the user menu) and verify that you can still see the User management and Group management tabs on the left.
If you can't see them, you've lost your Dynatrace admin permissions. Use the non-federated user account to change the configuration if you've run into any issues.
Dynatrace checks the value of the Security group claim attribute of each user following successful login. If a matching Dynatrace group is found, the user is added to the Dynatrace group and inherits all permissions of that group.
- When using SAML authorization, it's not required that you invite users to Dynatrace. If a user doesn't yet exist in Dynatrace, but during login one or more matching Dynatrace groups are found (via the security group claim name), the user is created automatically.
- Upon each login, the Dynatrace group assignment is updated based on the values specified in the Security group claim attribute.
SAML IdP configuration
Follow the examples linked here to configure any of these SAML identity providers (IdPs) to work with Dynatrace SSO.
Frequently asked questions (FAQ)
NameIdFormat must be
Whole messages need to be signed, including logout request and response. It's not sufficient to just sign the assertion part.
Upon logout, a global logout is triggered, including for your IdP, which then cascades to other services. Otherwise you would be logged out from Dynatrace, but it would be sufficient to just enter your email to reauthenticate.
If you want to disable it (not a good idea from a security standpoint), edit your metadata, remove all
SingleLogoutService tags, and upload the updated metadata.
You need two issuance transform rules, in this order:
- The first one uses the
Send LDAP Attributes as Claimsrule template and creates an outgoing claim type named
E-Mail Addressfrom an LDAP attribute in your attribute store containing the Dynatrace username (the user’s domain email address).
- The second one uses the
Transform an Incoming Claimrule template and creates an outgoing claim type
Name IDand outgoing name ID format
Pass through all claim valuesoption enabled.
If, after you authenticate with your IdP, you are redirected to a Dynatrace page such as We’ve run into technical difficulties… or 400 Bad Request, it's likely that there is a problem with the configuration.
The most common causes of this are:
- Your IdP doesn’t accept an
authNrequest using our
NameIdformat and returns an error response with status code
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress. You might also need a rule to create a
NameIdusing our format.
- You're using a
<saml:Attribute/>to return the Dynatrace username but the attribute wasn't recognized by Dynatrace; alternatively, we couldn't find it using
NameIDas we didn't recognize its format. See the previous question (
What claim rules do I need in AD FS on the Dynatrace relying party?) for the proper format.
- Dynatrace didn't trust your IdP SAML signing certificate. The IdP SAML metadata you uploaded did not contain a certificate for signing that matches the certificate in the assertion sent by your IdP. Verify that the certificate is in the metadata XML file that was uploaded to Dynatrace. If you're using a URL to upload the metadata, look at the contents generated by the URL. In some organizations, the SAML signing certificate must be requested separately and manually inserted into the metadata by saving the URL contents to a file, adding the signing certificate to the file, and then uploading the file to us.
- The response from the IdP isn't fully signed (assertion signature might be present, but it isn't sufficient).
- Your IdP doesn't accept some SAML objects or attributes that the SAML 2.0 specification describes as optional. Please contact Dynatrace Support.
Yes, users are added following successful authentication.
No, it can be removed after Dynatrace has successfully validated ownership of the domain.
Yes, but you need to do domain verification and create a configuration for each domain separately. Each domain configuration can use the same IdP metadata and settings.
No, a full DN contains commas and this is recognized as independent group names. The IdP should send the group name or group ID.
Yes, IDP-initiated login is supported. When a Dynatrace environment URL is sent in the
RelayState parameter, the user is redirected to the specified URL upon signing in.