Depending on your federation scope, follow one of the two procedures below to configure Okta as the SAML identity provider (IdP) for Dynatrace SSO.
This page describes the IdP (Okta) end of your SAML SSO configuration, not the Dynatrace end. Use it as part of the entire SAML configuration procedure for Dynatrace SaaS if you're using Okta.
While we do our best to provide you with current information, Dynatrace has no control over changes that may be made by third-party providers. Always refer to official third-party documentation from your IdP as your primary source of information for third-party products.
Choose a configuration procedure based on your federation scope.
My federation scope
Procedure to follow for Okta IdP configuration
global
Both procedures work for global federations. Choose one.
account
environment
I'm not sure
Through the Okta Integration Network, you can use an Okta-verified, pre-built configuration to integrate Dynatrace with your Okta IdP for SSO.
This procedure works only for configuring Dynatrace global federation with Okta as your IdP.
In the Okta interface, select Application from the main menu and select Add Application.
Search for Dynatrace and select Add.
Select Next.
In Sign On Methods, select SAML 2.0.
Optional Set Default Relay State to your default tenant URL or to other Dynatrace services from the *.dynatrace.com realm. If this is not defined, users after signing in will be redirected to the last accessed tenant or account/user profile.
Optional Set role as a Security group claim attribute. If configured, Okta will send assigned groups within the SAML Request.
To manage group membership in Okta with SAML Authorization in Dynatrace, this must be configured.
Matches regex and enter .* as the value to have all groups assigned to the user sent with the SAML request.Optional Select Enable Single Logout and upload a certificate (Browse and Upload) to enable global single logout. The certificate is provided in Okta's Dynatrace configuration. You need to be signed into the Okta Admin Dashboard.
This section describes how to manually configure Okta as your IdP for all Dynatrace federation scopes (global, account, and environment).
This procedure works for all Dynatrace federation scopes (global, account, and environment) when using Okta as your IdP.
Download your Dynatrace federation Service Provider metadata XML file.
In the General settings, you define the basic properties for your configuration. They describe the connection between your Okta Identity Provider (IdP) and Dynatrace.
It's important to use values from the Dynatrace Service Provider metadata XML file you downloaded in the first step. Set properties as described below.
Property
Value
Notes
Single sign on URL
Location attribute value of AssertionConsumerService XML node in your Dynatrace Service Provider metadata
selected.not selected.Audience URI (SP Entity ID)
entityID attribute value of EntityDescriptor XML node in your Dynatrace Service Provider metadata
Name ID format
EmailAddress
Application username
Email
Update application username on
Create and update
Select Show Advanced Settings. Set properties as described below:
Property
Value
Notes
Response
Signed (required)
The entire SAML message must be signed (signing only SAML assertions is insufficient and generates a 400 Bad Request response).
Assertion Signature
Signed (optional)
Dynatrace ignore assertions signatures
Signature Algorithm
RSA-SHA256
Digest Algorithm
SHA256
Assertion Encryption
Unencrypted (required)
Enable Single Logout and Single Logout URL
If you want to enable single logout service with Dynatrace SSO:
Location attribute value of SingleLogoutService XML node in your Dynatrace Service Provider metadataThere are two SingleLogoutService XML nodes in your Dynatrace Service Provider metadata (for HTTP-POST and HTTP-Redirect bindings). They have the same Location attribute value set, so it doesn't matter which one you use.
SP Issuer
entityID attribute value of EntityDescriptor XML node in your Dynatrace Service Provider metadata
The value is the same as for Audience URI (SP Entity ID) from the General configuration step
Signature Certificate
Certificate from X509Certificate XML node value in your Dynatrace Service Provider metadata XML file. It must be an X509Certificate file wrapped with a header.
If your Dynatrace Service Provider metadata XML file contains two certificates, choose the certificate having KeyName equals Dynatrace Certificate 2023.
The certificate file required by Okta for SSO application configuration can be converted from an X509Certificate using, for instance, this online tool. The result should be just an X509Certificate wrapped with a header.
Configure attribute statements to enable SAML authorization in Dynatrace SSO.
Values displayed here are only examples.

Attribute names need to match the Dynatrace federated attribute values on the Dynatrace Single sign-on page:
First name attributeLast name attributeSAML Group attributeYou can configure Group Attribute Statements filtering using Okta's proprietary expression language. For example, .* means that all groups assigned to the user will be sent with the SAML request.