Skip to main content

Domo (IdP-initiated) Integration Guide


Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Domo.


1. Have a Domo account with SAML capabilities enabled

2. Create a New Realm for the Domo integration in the SecureAuth IdP Web Admin

3. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined

  • Data – an enterprise directory must be integrated with SecureAuth IdP

  • Workflow – the way in which users will access this application must be defined

  • Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined

SecureAuth IdP Configuration Steps



1. In the Profile Fields section, map the directory field that contains the user's email address to the SecureAuth IdP Email 1 Property

2. Map the directory field that contains the user's Domo ID to the SecureAuth IdP Property

For example, add the Domo ID directory field to the Email 2 Property if it is not already contained somewhere else

3. Map the directory field that contains the user's Full Name to the SecureAuth IdP Aux ID 1 Property (e.g. displayName in AD)


Refer to the Optional Configuration Steps below if there is no directory attribute that contains the user's full name, or to configure the realm differently and not using the directory to contain the information


Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Optional Configuration Steps

Follow the optional steps below in lieu of step 3

Post Authentication


4. In the Post Authentication section, select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown

5. An unalterable URL is auto-populated in the Redirect To field, which appends to the domain name and realm number in the address bar (Authorized/SAML20IdPInit.aspx)

User ID Mapping


6. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Domo ID (Email 2)

7. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if Domo requires it, which the Service Provider (SP) provides

SAML Assertion / WS Federation


8. Set the SAML Consumer URL to https://<COMPANY>

9. Set the WSFed/SAML Issuer to a Unique Name that is shared with Domo

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Domo side

10. Set the SAML Recipient to https://<COMPANY>

11. Set the SAML Audience to https://<COMPANY>

12. Set the SAML Offset Minutes to make up for differences between devices

13. Set the SAML Valid Hours to limit for how long the SAML assertion is valid

14. Select PasswordProtectedTransport from the AuthnContext Class dropdown


No configuration is required for the WSFed Reply To/SAML Target URL or SP Start URL fields


15. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, then click Select Certificate and choose the preferred certificate

16. Provide the Domain in order to Download the Metadata File, which is sent to Domo

SAML Attributes / WS Federation


17. Set the Name of Attribute 1 to email

18. Select Email 1 from the Value dropdown (step 1)

19. Set the Name of Attribute 2 to name

20. Select Aux ID 1 from the Value dropdown (step 3)


If followed the Optional Configuration Steps instead of step 3, then select Custom Token Value from the Value dropdown


Click Save once the configurations are completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.