Follow the examples below to configure Google Workspace as the SAML identity provider (IdP) for Dynatrace SSO.
This page describes the IdP (Google Workspaces) 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 Google Workspace.
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.
Navigate to the Google Workspace Admin panel and choose Apps > SAML apps from the menu.
Choose to add a new SAML application to open a pop-up configuration wizard.
On the Enable SSO for SAML Application page, select Setup my own custom App.
On the Google IdP Information page, in the IDP metadata section (Option 2), click Download to download the IdP metadata as an XML file. This will be needed when configuring single sign-on in Dynatrace.
On the Basic information for your Custom App page, provide an intuitive Application Name.
On the Service Provider Details page, enter Service Provider (SP) details as follows:
ACS URL |
|
Entity ID |
|
Start URL | Leave this empty for now |
Signed Response | Select this check box. |
NameID | Leave this as is. |
NameID format | Leave this as is. |
This information can also be found in Dynatrace SSO metadata at https://sso.dynatrace.com/sso/metadata.
On the Attribute Mapping page, add mappings for FirstName
and LastName
as shown in the example. (You'll need to add a third mapping later for Groups
, which is described in the Preparing group mapping section that follows.)
By default, Google Workspace doesn't offer a way to send user groups through SAML. This is required for mapping to certain groups/permissions in Dynatrace. The only fields that can be delivered by SAML are as in this example:
This doesn't allow the Google Workspace administrator to provide a list of groups or permissions that the user should have in Dynatrace.
Google suggests that you add a custom schema to user accounts. This enables you to add multiple group entries that, upon being sent via SAML, are mapped correctly to groups and permissions in Dynatrace.
https://developers.google.com/admin-sdk/directory/v1/reference/schemas/insert?authuser=1
my_customer
, which automatically uses this Google account's ID.{"schemaName": "DynatraceSSO","displayName": "DynatraceSSO","fields": [{"fieldType": "STRING","fieldName": "UserRole","displayName": "UserRole","multiValued": true,"readAccessType": "ADMINS_AND_SELF"}]}
FirstName
and LastName
were added previously.Role
attribute to DynatraceSSO
and UserRole
.
This will make Google send all of the entries in DynatraceSSO
/UserRole
for a certain user as an attribute in SAML, which Dynatrace SSO will use to assign permissions upon a federated login. The user roles can be applied to each user separately using the user configuration screen in Google Workspace.
User roles can be applied to every user separately using the User information screen in Google Workspace.
You can map these roles in Dynatrace Account Management to certain permissions as needed.
Note that in Google Workspace, UserRole
has to have the same value as the Security group claim name
in Dynatrace Account Management (for example, DynatraceTenantViewer
and DynatraceAccountAdmin
).
Say you've set up two groups in Dynatrace Account Management and have a group called Main Account Admin
, which is assigned a federated user by the Security group claim name DynatraceAccountAdmin
.
If you now attach the DynatraceAccountAdmin
UserRole
to any user in Google Workspace, that user will be assigned the permissions of the Main Account Admin
group in Dynatrace Account Management.
Upon setting up the SAML apps configuration in Google Workspace correctly, the SAML request sent from Google Workspace should contain the configured groups as SAML attributes.