If your organization uses a SAML-based identity provider (IdP) for authentication, you can configure it to work with the Data Activation platform. When you enable IdP authentication, users in your organization log in through your IdP instead of using a platform password.
Setting up IdP authentication requires coordination with the Supermetrics support team to finalize the configuration.
Before you begin
You must have admin access to the Data Activation platform.
Your identity provider must support SAML authentication.
If you use the Data Activation REST API, set up API key authentication before you enable IdP. After you enable IdP, password-based API authentication will no longer work. See How to connect to REST API using tokens.
Instructions
Contact our support team and provide the following:
A list of email domains for the users who should authenticate through the IdP.
A request for your client ID. Our support team will provide this.
In your IdP platform, create a new SAML application and configure it with the following settings:
Authentication type: SAML
Single sign-on URL:
https://admin.relay42.com/login/saml2/sso/{CLIENTID}— replace{CLIENTID}with the client ID provided by our support team.Recipient URL and Destination URL: same as the single sign-on URL above.
Audience restriction (also called Service Provider Entity ID, SP Entity ID, or SP Issuer depending on your IdP): set to
Relay42.Name ID format:
EmailAddress
Save the configuration in your IdP and download the metadata XML file.
Send the metadata XML file to our support team. We’ll finalize the configuration on our end.
Set up single logout (optional)
If your IdP supports single logout (SLO) and you want to enable it, contact our support team. We’ll provide Supermetrics' signature certificate and the URL you need to configure in your IdP.
What changes after you enable IdP authentication
After IdP authentication is enabled for your organization:
Users whose email domain is on the configured list are automatically assigned to your client account and redirected to your IdP login portal.
Those users can no longer log in with a platform password.
API authentication with a password also stops working. Any processes that call the Data Activation REST API must use API key authentication instead. See How to connect to REST API using tokens.