![]() |
VOOZH | about |
See the following instructions to synchronize your Datadog users with Okta using SCIM.
For the capabilities and limitations of this feature, see SCIM.
SCIM in Datadog is an advanced feature available with the Infrastructure Pro, Infrastructure Enterprise, and Startup plans
This documentation assumes your organization manages user identities using an identity provider.
Datadog strongly recommends that you use a service account application key when configuring SCIM to avoid any disruption in access. For further details, see using a service account with SCIM.
When using SAML and SCIM together, Datadog strongly recommends disabling SAML just-in-time (JIT) provisioning to avoid discrepancies in access. Manage user provisioning through SCIM only.
Note: If you already have Datadog configured with Okta, select your existing Datadog application.
https:///api/v2/scim Note: Use the appropriate subdomain for your site. To find your URL, see Datadog sites.To provision a user’s Datadog role (built-in or custom) through SCIM, add an explicit mapping for the roles attribute. Okta does not map this attribute by default.
Datadog’s SCIM role support follows the SCIM multi-valued attribute convention defined in RFC 7643, using the role UUID as value and the role name as display:
{
"roles": [
{ "value": "<DATADOG_ROLE_UUID>", "display": "<DATADOG_ROLE_NAME>" }
]
}
roles attribute:roles attribute to the Datadog roles attribute.If a SCIM request sends multiple roles, Datadog provisions only the roles that match a role in your organization. If none match, the user falls back to the org default role (Standard), and unmatched roles are logged to Audit Trail. For more details, see SCIM.
With Managed Teams, you control the core provisioning of a Datadog Team — its name, handle, and membership — through the identity provider. The setup process differs depending on whether the team already exists in Datadog.
Note: Users must exist in Datadog before you can add them to a team. Therefore, you must assign users to the Datadog app in Okta to ensure that they are created in Datadog through SCIM. Assign the Datadog application to your Okta group to ensure that all team members are created in Datadog automatically.
To verify that the operation completed successfully, navigate to the Teams list in Datadog. Search for a Datadog Team matching the Okta group you configured. Verify that the team exists in Datadog and is managed externally. It may take a minute or two before the team appears in Datadog.
You can map an existing Datadog Team to an Okta group. Establishing a link from the Okta group to the Datadog Team causes the Datadog Team to be managed by Okta going forward.
Note: In order to synchronize an existing Datadog Team with an Okta group, the two names must match exactly.
Note: When you select Create group, Okta displays a No match found message. You can ignore this message and proceed with creating the group to establish synchronization.
You have two options for disconnecting an Okta group from a Datadog Team, with different impacts on the Datadog Team membership.
This procedure allows you to manage team membership in Datadog instead of Okta. The team members stay unchanged.
This procedure allows you to manage team membership in Datadog instead of Okta and removes the team members from the Datadog Team.
Note: Contrary to the name of the option, selecting Delete the group in the target app does not delete the team in Datadog. Instead, it removes all members from the team and removes the link between the group in Okta and the Datadog Team.
Additional helpful documentation, links, and articles:
| |