ExactTarget (IdP-initiated) Integration Guide
Introduction
Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to ExactTarget.
Prerequisites
1. Have an ExactTarget account with SAML capabilities enabled
2. Create a New Realm for the ExactTarget 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
Data
 |
1. In the Profile Fields section, map the directory field that contains the user's ExactTarget ID to the SecureAuth IdP Property
For example, add the ExactTarget ID directory field to the Email 2 Property if it is not already contained somewhere else
Warning
Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes
Post Authentication
 |
2. In the Post Authentication section, select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown
3. 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
 |
4. Select the SecureAuth IdP Property that corresponds to the directory field that contains the ExactTarget ID (Email 2)
5. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)
Select a different option if ExactTarget requires it, which the Service Provider (SP) provides
SAML Assertion / WS Federation
 |
6. Set the SAML Consumer URL to https://auth.s1.exacttarget.com/Shibboleth.sso/SAML2/POST
7. Set the WSFed/SAML Issuer to a Unique Name that is shared with ExactTarget
The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the ExactTarget side
8. Set the SAML Recipient to https://auth.s1.exacttarget.com/Shibboleth.sso/SAML2/POST
9. Set the SAML Audience to https://sp.exacttarget.com/shibboleth-sp
10. Set the SAML Offset Minutes to make up for differences between devices
11. Set the SAML Valid Hours to limit for how long the SAML assertion is valid
No configuration is required for the WSFed Reply To/SAML Target URL or SP Start URL fields
 |
12. 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
13. Provide the Domain in order to Download the Metadata File, which is sent to ExactTarget
Warning
Click Save once the configurations are completed and before leaving the Post Authentication page to avoid losing changes
Forms Auth / SSO Token
 |
14. Click View and Configure FormsAuth keys / SSO token to configure the token / cookie settings and to configure this realm for SSO
These are optional configurations
 |
1. If SSL is required to view the token, select True from the Require SSL dropdown
2. Choose whether SecureAuth IdP will deliver the token in a cookie to the user's browser or device:
UseCookies enables SecureAuth IdP to always deliver a cookie
UseUri disables SecureAuth IdP to deliver a cookie, and instead deliver the token in a query string
AutoDetect enables SecureAuth IdP to deliver a cookie if the user's settings allow it
UseDeviceProfile enables SecureAuth IdP to deliver a cookie if the browser's settings allow it, no matter the user's settings
3. Set the Sliding Expiration to True if the cookie remains valid as long as the user is interacting with the page
4. Set the Timeout length to determine for how many minutes a cookie is valid
No configuration is required for the Name, Login URL, or Domain fields
 |
5. No changes are required in the Validation field, unless the default value does not match the company's requirement
If a different value is required, select it from the dropdown
6. No changes are required in the Decryption field, unless the default value does not match the company's requirement
If a different value is required, select it from the dropdown
No configuration is required for the Validation Key or Decryption Key fields
 |
7. Enable the cookie to be Persistent by selecting True - Expires after Timeout from the dropdown
Selecting False - Session Cookie enables the cookie to be valid as long as the session is open, and will expire once the browser is closed or the session expires
No configuration is required for the Pre-Auth Cookie, Post-Auth Cookie, or the Clean Up Pre-Auth Cookie fields
Warning
Click Save once the configurations have been completed and before leaving the Forms Auth / SSO Token page to avoid losing changes
To configure this realm for SSO, refer to SecureAuth IdP Single Sign-on Configuration
To configure this realm for Windows Desktop SSO, refer to Windows desktop SSO configuration.