Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.
No ratings
Vedanth_BK
Saviynt Employee
Saviynt Employee

Disclaimer

The integration was either created by Saviynt or by Saviynt community users and verified by Saviynt. The integration is available “as is” and falls under standard connectors support for REST, SOAP, JDBC, LDAP, PowerShell, Jar, and Saviynt Connector Framework.

 

Contents

Preface

This guide describes the integration between Saviynt Enterprise Identity Cloud (EIC) and SAP Marketing Cloud.

Audience

This guide is intended for administrators and target application integration teams responsible for implementing a secure integration service with SAP Marketing Cloud.

Introduction

SAP Marketing Cloud is a comprehensive cloud-based marketing solution provided by SAP, a leading enterprise software company. It is designed to help businesses effectively plan, execute, and analyze their marketing activities across various channels and touchpoints.SAP marketing cloud provides SOAP-based web service API’s for CRUD operations of business users from external systems.

The SOAP connector enables you to seamlessly integrate with SAP Marketing Cloud to manage user lifecycle and govern access to their Role.

For more information about different connectors in EIC, see Saviynt Enterprise Identity Cloud Connectors.

Note: This guide provides information about using the SAP Marketing Cloud(SOAP) connector for performing operations listed in the Supported Features.

 

The SAP Marketing Cloud integration supports the following features:

 
sap_mc_features.png
 

Supported Software Versions

 

Software

Version

EIC

Release v4.5 and later

 

Understanding the Integration between EIC and SAP Marketing Cloud

You must create an integration between EIC and the collaboration platform hosted by the target application to perform the import and de-provisioning tasks. The following components are involved in the integration:

  • SAP Marketing Cloud is the target application for which EIC manages the identity lifecycle. SAP Marketing Cloud integrates with EIC through the connector to manage accounts and access.

  • Objects are imported as entitlement types into EIC.

  • Security System represents the connection between EIC and the target application.

    • It comprises an endpoint, which is the target application for which you want EIC to manage the identity repository.

    • It provides application instance abstraction from connectivity including high-level metadata. For more information about creating a security system, see Creating a Security System.

  • Endpoint is an instance of an application within the context of a security system.

    • It is the target application or application from which the connector performs provisioning or de-provisioning of identity objects, such as users, accounts, and entitlements.

    • It is mandatory to create an endpoint after creating the security system.
      You can associate a single security system with multiple endpoints if the deployment involves modeling multiple isolated virtual applications (based on sets of specific entitlements according to certain categories) within a single application instance. For more information about creating an endpoint, see Creating an Endpoint for the Security System.

  • The connector is a software component that enables the communication between EIC and the target application. It provides a simplified integration mechanism where in some instances you only need to create a connection with minimal connectivity information for your target application. The (SOAP-based) Connector is used for provisioning accounts and access through the SOAP APIs. For more information about creating a connection, see Creating a Connection.

  • Job Scheduler is a software component that executes a job based on the configured schedule to perform provisioning operations from EIC.
    When a provisioning job is triggered, it creates provisioning tasks in EIC. When these tasks are completed, the provisioning action is performed on the target application through the configured connector. If you want to instantly provision requests for completing the tasks without running the provisioning job, you must enable Instant Provisioning at the security system level and the Instant Provisioning Tasks global configuration. For more information about the jobs used by the connectors in the SAP Marketing Cloud integration.

Integration Architecture

EIC uses a SOAP connection for integrating with SAP Marketing Cloud for importing data and for performing provisioning and de-provisioning tasks. The SOAP connection uses the SOAP protocol to communicate with the SOAP interface of the SAP Marketing Cloud. 

The following diagram illustrates the integration architecture and communication with the target application.  

 

SAP_MC_ARCH.png

Figure: SAP Marketing Cloud Integration Architecture

Setting Up the Integration

Prerequisites

Ensure that the following prerequisites are met:

  • Create a Communication User.

SAP_PR_NEW_1_NEW.png

 
  • Create a communication system

 

sap_mc_pr2_new.png

  • Create communication arrangement based on predefined scenario to map user, and system and generate service WSDL for external system consumption

 

sap_mc_pr3.png

 

Creating a Connection

Connection refers to the configuration setup for connecting EIC to target applications. For more information about the procedure to create a connection, see Creating Connections.

Understanding the Configuration Parameters

While creating a connection, you must specify connection parameters that the connector uses to connect with the target application, define the type of operations to perform, the target application objects against which those operations are performed, and the frequency of performing them. In addition, you can view and edit attribute mappings between EIC and the target application, predefined correlation rules, and provisioning jobs and import jobs.

Configuration Parameters for Account and Access Import

The connector uses the following parameters for creating a connection and for importing account and access from the target application:

Connection Parameters
 

Parameter

Description

Example Configuration

Mandatory?

Connection Name 

Specify the name to identify the connection.

-

Yes

Connection Description

Specify the description for the connection.

-

No

Connection Type

Select the connection type as SOAP.

-

Yes

Default SAV Role 

Specify this parameter to assign the SAV role for the connection.

The SAV role is a role in EIC that assigns specific access to users.

This parameter is valid only for importing users.

Sample value: User assigned with the ROLE_ADMIN role, has access to all the sections of EIC.

-

No

Email Template

Specify this parameter to select an email template for sending notifications.

Email templates provide immediate trigger of emails to a user based on actions performed. Email informs user about the action performed and if critical, needs immediate action from the user.

-

No

ConnectionJSON

Specify this parameter to create a connection.

 

 

Yes

SOAP_OR_XML

Specify the type of Endpoint - SOAP or XML based.
Default is SOAP

SOAP

Yes

 
Import Parameters
 

Parameter

Description

 

Recommended Configuration

Mandatrory

ACCOUNTS_IMPORT_JSON

Specify this parameter to reconcile the accounts and entitlements .

 

Yes

 
Configuration Parameter for Provisioning
 

Parameter

Description

 

Recommended Configuration

Support for Binding Variables?

Support for Java Ternary Operations?

CREATEACCOUNTJSON

Specify this parameter to Create an account. 

 

The bindings supported are:

  • task

  • user

  • dynamicattributename

  • manager

  • requestor

  • approverMap

  • taskowner

  • endpointowner

  • endpoint

  • accountName

  • randomPassword

Yes

UPDATEACCOUNTJSON

Specify this parameter to Update an account. 

  • task

  • user

  • dynamicattributename

  • manager

  • requestor

  • approverMap

  • taskowner

  • endpointowner

  • endpoint

  • accountName

  • randomPassword

  • account

Yes

DELETECCOUNTJSON

Specify this parameter to Delete an account. 

 
  • task

  • user

  • dynamicattributename

  • manager

  • requestor

  • approverMap

  • taskowner

  • endpointowner

  • endpoint

  • accountName

  • randomPassword

  • account

Yes

GRANTACCESSJSON

Specify this parameter to add access to an account.

  • task

  • user

  • dynamicattributename

  • manager

  • requestor

  • approverMap

  • taskowner

  • endpointowner

  • endpoint

  • accountName

  • randomPassword

  • entitlement

  • account

  • role

  • entTask

  • entitlementSet

  • newEntitlementMap

  • allEntitlementMap

  • rolesSet

Yes

REVOKEACCESSJSON

Specify this parameter to remove access to an account.

 

  • task

  • user

  • dynamicattributename

  • manager

  • requestor

  • approverMap

  • taskowner

  • endpointowner

  • endpoint

  • accountName

  • randomPassword

  • entitlement

  • account

  • role

  • entTask

  • entitlementSet

  • newEntitlementMap

  • allEntitlementMap

  • rolesSet

Yes

 

 

Importing Connection Package

Transporting Packages aka T2P connection packages help you build the connection with pre-defined JSONs, this can be used if your tenant does not already have out-of-the-box connection templates available. Here are the steps to import the SAP Marketing Cloud connection package.

  • Download the connection package.

  • Navigate to Admin → Transport → select Import Package.

  • Browse the downloaded package and Import.

  • Navigate to Admin → Connections → Select “SAP Marketing Cloud ” Connection.

  • Edit the connection with your SAP Marketing Cloud tenant details.

Creating a Security System

The security system represents the connection between EIC and the target application. For more information on creating a security system, see Creating a Security System.

Creating an Endpoint for the Security System

Endpoint refers to the target application used to provision accounts and entitlements (access). For more information on creating an endpoint, see Creating Endpoints.

Using the SAP Marketing Cloud Integration

You can use the SAP Marketing Cloud integration for performing import and provisioning operations after configuring it to meet your requirements. 

Guidelines for Using the Integration

You must apply the following guidelines for configuring import: 

  • Run the account import before running the access import.

  • Map all SAP Marketing Cloud attributes to EIC account attributes using ImportAccountEntJSON.

You must apply the following guidelines for configuring provisioning:

  • Use Java ternary operators if you want to add conditions in the provisioning parameters. You can use Java operations to tweak any attributes by using if-else conditions, substrings, or operators in the JSON for provisioning.

Configuring Import Operations

  • Full account import: When configuring the connection for the first time, first perform the full import to import all existing accounts from the target application to EIC. To perform the full import, the invoke API gets a response from the target application and maps the attributes in the target application with attributes in EIC. As part of this process, the deleted accounts are also identified and marked as suspended from import service.

  • Full Access import: When configuring the connection for the first time, first perform the full import to import all existing access from the target application to EIC. To perform the full import, the invoke API gets a response from the target application and maps the attributes in the target application with attributes in EIC. As part of this process, the deleted entitlements are also identified and marked as inactive.

The import jobs are automatically created in EIC after you create a connection an integration.

Importing Accounts and Accesses

You must import accounts after the users are available in EIC.

To import accounts: 

  1. Specify the connection and import parameters.
    Note: Ensure that the connection type is selected as SOAP.

  2. Configure the Application Data Import (Single Threaded) job to import accounts and access. For more information, see Data Jobs.

Configuring Provisioning and Deprovisioning

Provisioning is automatically enabled when a connection is configured. For detailed information about performing provisioning tasks, see Access Request System.

To provision objects to the target application:

  1. Specify the connection and provisioning parameters. For more information, see Configuration Parameters for Provisioning.
    Note: Ensure that the connection type is selected as SOAP.

  2. Configure the Provisioning job (WSRETRY). For more information, see Provisioning Jobs.

When a provisioning job is triggered, it creates provisioning tasks in EIC. When these tasks are completed, the provisioning action is performed on the target application through the connector.

Troubleshooting

To troubleshoot common problems with connectors, answer frequently asked questions, and provide solutions to a few common issues you might encounter while configuring or working with connectors, see Common Troubleshooting Guide for Connectors.

To troubleshoot common problems or obtain answers to frequently asked questions for SOAP connectors, see the  SOAP Connector guide.

Note: Ensure that you record the token expiry duration during the initial token generation. The connection may fail if the token is not refreshed.

Version history
Last update:
‎06/16/2023 04:57 AM
Updated by:
Contributors