New features and changes in version 9.1.1

Support added for SAML 2.0 based federated authentication

Marketing Platform supports SAML (Security Assertion Markup Language) 2.0 federated authentication, which enables single sign-on access among diverse applications.

You can use federated authentication to implement single sign-on between IBM EMM applications and other HCL applications or third-party applications

The Marketing Platform installation includes the following components that support federated authentication.

• An identity provider server
• A client JAR file that you can use with Java applications to generate and parse SAML 2.0 assertions. The Java products that you integrate with IBM EMM use the assertions to communicate with the identity provider server.

Contact your HCL representative to learn more about this feature.

Audit event tracking and reporting

A new Audit Events report is introduced with the 9.1.1 release of Marketing Platform. You can configure which audit events are tracked and assign a severity level to each tracked event.

The Audit Events report provides a convenient way to view the tracked events. You can configure the content of the report, filter the information shown in the report, and export report data.

Two kinds of audit events are tracked:

• Security related events such as changes to user status, group memberships, and permissions
• Changes to IBM EMM configuration properties that are managed on the Settings > Configuration page

You must have the AdminRole or PlatformAdminRole role in Marketing Platform to configure the Audit Events report and audit backups or to view the report.

Data filter enhancement

The data filter feature has been enhanced to make it easier to configure data filters based on user logins.

When you have a filter based on user logins, you can now use the #user_login# wild card to assign data filters to users or groups of users. At run time, the wild card value is replaced by the current user's login. This eliminates the step of creating one filter for each user.

Here is an example of the XML you would create to add all members of the FieldMarketers group to a data filter.

<DataFilter>
	<configId>1</configId>
    <id>1</id>
    <fieldConstraints>
      <FieldConstraint>
        <logicalFieldId>3</logicalFieldId>
        <expression>#user_login#</expression>
			<!-- This is the wild card. -->
      </FieldConstraint>
     </fieldConstraints>
</DataFilter>

<AssignmentByName>
     <namespaceId>1</namespaceId>
     <dataObjectId>1</dataObjectId>  
		<!-- This is a reference to the filter.-- >
     <principalType>2</principalType> 
		<!-- This is the type of assignment: 1 is for assigning to a user,
			2 is for assigning to a group of users. -->
     <principalName>FieldMarketers</principalName> 
		<!-- This is the name of the group to which you assign the filter.-->
</AssignmentByName>

Note that you still have to create the XML to set up the data filters themselves, as described in the HCL Marketing Platform Administrator's Guide.

Interaction History and Attribution Modeler are not supported

Interaction History and Attribution Modeler are not available for version 9.1.1. Enterprise Marketing Management products on version 9.1.1 do not support integrations with version 9.1.0 of Interaction History and Attribution Modeler.

IBM ExperienceOne Knowledge Center

You can view common tasks, troubleshooting, and support documentation the same way you have in prior releases by using the Help menu in each product, including Help > Product documentation or Help > Help for this page. To get documentation on all other IBM products, use the IBM Knowledge Center at http://www.ibm.com/support/knowledgecenter/.