System for Cross-domain Identity Management (SCIM) is an open standard for automating the exchange of user identity information between identity domains or IT systems. You can configure Dynatrace SaaS to be provided with user identity information automatically from your organization's identity provider (IdP) through SCIM.
SCIM requirements and supported features
Dynatrace supports SCIM 2.0 and GET, POST, PATCH, PUT, and DELETE operations for both User and Group resources.
For authentication, SCIM requires Bearer token in Authorization header.
SCIM is configured for the account and domain scopes. At least one domain ownership verification is required for the account.
Only users whose email domains have been verified for ownership can be synchronized with Dynatrace via SCIM.
Required and supported SCIM attributes:
SCIM Attribute Type userName email format name.givenName string name.familyName string active boolean
userName must be persistent. Dynatrace does not support user email change.
Verify your ownership of the domain
Before you can proceed with SCIM configuration, you need to prove ownership of the domain. Verification is based on a DNS TXT Record check.
For the account, it is sufficient to verify the domain once. If a domain has been verified for SAML, it will be valid for SCIM as well.
To verify ownership of a domain
From the User menu on the right-hand side of the menu bar, select Account settings.
Select Identity management and SCIM configuration from the menu on the left.
In the Verify domain section, enter the Domain that you want to verify, beginning with an
Select Copy and add the TXT resource record to your domain’s DNS configuration.
Select Verify so Dynatrace can verify that the record was added to your domain’s DNS.
Propagation time: It typically takes a few minutes for the record to propagate through the DNS system and the value to become available for Dynatrace to verify. In edge cases, it may take up to 24 hours.
Example: Verify domain
After successful verification, the domain is listed in Verified domains.
Example: Verified domains
If people in your organization use more than one domain to sign in (for example,
@uk.mycompanyname.com), you can repeat this procedure for the additional domains. When the additional domains are successfully verified, they are added to the Verified domains list.
Get Dynatrace SCIM endpoint and create secret token
Use this procedure to get the Dynatrace SCIM Base Url for your account and create a secret token.
Important: The token is revealed only once during generation time. Copy and paste it into a secure location. If you lose it, you have to generate a new one and replace it in your application.
In Dynatrace Account settings
Select Identity management > SCIM configuration from the navigation menu.
Example: Select 'SCIM configuration'
Click Generate token with an optional Description (or you can add a description for the token later on).
Example: Generate token
Under Generate token, click Copy to copy the token to your clipboard, and then paste it into a secure location for later use.
Example: Copy token
Dynatrace SCIM supports Bearer Token Authentication only. Example:
Header Value Authorization Bearer dt0s01.XFNYASDX.XFJWNDTUXJ6PKHEHDDVKXV2K73ZDGWUFS6GKHGAFKE2DUG3JYCFXJUAGLXTN6ENX
The SCIM endpoint required for SCIM configuration in your application is added to the List of tokens.
Example IdP-specific instructions
To continue integrating Dynatrace SCIM with your IdP, select the procedure appropriate for your IdP:
Frequently asked questions (FAQ)
No, an email address can't be changed by SCIM. Any requests to update an email address are ignored.
You can generate up to 10 SCIM authentication tokens. For security reasons, we strongly recommend that you delete all unused tokens.
Yes, you can provision as many users from different email domains as you need, as long as all of their domains have been verified. You can verify multiple domains for a single account.
No. Some IDPs, like Azure AD, allow multiple groups with the same name in a single account. For Dynatrace SSO, however, each group name in an account must be unique.