SAP NetWeaver. MDM Security Guide. SAP NetWeaver MDM 7.1 SP08 Document Version 3.1 April 3, 2012

Transcription

1 SAP NetWeaver MDM Security Guide SAP NetWeaver MDM 7.1 SP08 Document Version 3.1 April 3, 2012

2 October 2011 Copyright 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. Documentation on SAP Service Marketplace You can find this documentation at service.sap.com/instguidesnw04 April 2012

3 October 2011 Typographic Conventions Type Style Example Text Represents Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Icons Icon Meaning Caution Example Note / Tip Recommendation Syntax Example text EXAMPLE TEXT Example text Example text Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER. April 2012

4 Document History Document Version Description of Change 3. 1/ April 2012 Consolidated information from the MDM Console Reference guide into the following sections: o LDAP Support (page 10) o Authentication of Trusted Connections (page 23) 3.0 / September 2011 Guide updated for MDM 7.1 SP08 Secure Trusted Connection support added. See Authentication of Trusted Connections (page 23). New mds.ini option added for securing connections to Microsoft Active Directory LDAP Server. See Secure Connection to Microsoft Active Directory Configuration (page 23). Default Admin user password changed to sapmdm. See Standard User (page 9). New CLIX commands added for password management operations. See CLIX Commands for Managing Passwords (page 9). New CLIX command added for emergency Admin user password creation. See Emergency User Concept (page 10). 2.0 / May 2011 Guide updated for MDM 7.1 SP07 SSL support added. See Network and Communication Security (page 17). April 2012

5 Contents MDM SECURITY GUIDE COMPONENTS OF SAP NETWEAVER MDM USERS, ROLES AND AUTHENTICATION Users Roles and Authorizations Roles Authorizations Predefined Users, Roles and Passwords Single Sign-On Support Authentication and SSO-like Feature in MDM Java Components User Management Trusted Connection iviews and UWL Authentication and the SSO-like Feature MDM Web Services Generator Security MDM Web Services Security Password Change Enforcement Minimum Length of Password Password Validity Timeframe Strong and Secure Passwords Deactivating Authorization Credentials Password History Locking User Accounts CLIX Commands for Managing Passwords User Administration Tools Standard User Emergency User Concept LDAP Support What is LDAP? How LDAP Works Basic MDM LDAP MDM LDAP Fields LDAP Access MDM LDAP Algorithm (Basic) MDM LDAP Algorithm (Alternative) MDM LDAP Algorithm (Fallback) MDM Architecture in LDAP Restrictions and Limitations LDAP Errors and MDM NETWORK AND COMMUNICATION SECURITY Securing Communication Channels Using SSL Secure Connection Prerequisites Configuring MDM Servers for SSL MDS Configuration Auxiliary and Slave Server Configuration Connecting Securely from MDM Clients Connecting Securely from MDM Console April 2012

6 3.4.2 Connecting Securely from other Rich Clients Connecting Securely from MDM CLIX Connecting Securely from MDM APIs Connecting Securely from MDM Web UIs Connecting Securely from MDM Web Services Connecting Securely from MDM PI Adaptor Connecting Securely from MDM Enrichment Contoller Server Landscape Communication Channels Used Client/MDS Communication MDS/Database Server Communication Network Ports Used Remote Function Call Secure Connection to Microsoft Active Directory Configuration Authentication of Trusted Connections Trusted Connection Configuration Parameters IP-Based Trusted Connections How IP-Based Trusted Connections Work SSL-Based Trusted Connections Configuring SSL-Based Trusted Connections ABAP API Trusted Connection: Java/.NET Trusted Connection: AUTHORIZATION CONCEPTS AND MANAGEMENT Separation of Duties Support Change Log for Authorization Management Change Log Archiving AUDITING Logging of Security-Relevant Information CONTENT SECURITY Document and File Upload MDM FILE LOCATIONS AND FILE SYSTEM SECURITY Session IDs User Session Lock REGULATORY COMPLIANCE Person-Related Data April 2012

7 Components of SAP NetWeaver MDM Users MDM Security Guide Target Audience Technology consultants System administrators CIOs Security experts This document is not included as part of the Installation Guides, Configuration Guides, Technical Operation Manuals, or Upgrade Guides. Such guides are only relevant for a certain phase of the software lifecycle, whereby the Security Guides provide information that is relevant for all phases of the lifecycle. Scope of this Guide This Security Guide describes the security for the SAP NetWeaver MDM component only. For information about the other SAP components used for the MDM scenarios, see SAP Service Marketplace at service.sap.com/installmdm71 Master Guide. Fundamental Security Guides See the corresponding Security Guides of the SAP components that are a part of the MDM scenarios. Application Guide Most Relevant Sections or Specific Restrictions SAP ECC 6.0 SAP ERP 2005 Security Guide In the SAP ERP 2005 Security Guide, choose Security Guides for SAP ECC 6.0. SAP NetWeaver Process Integration 7.1 Operating Systems and Database Platforms SAP NetWeaver Security Guide SAP NetWeaver Security Guide In the SAP NetWeaver Security Guide, choose Security Guides for SAP NetWeaver Products SAP Security Guide PI. In the SAP NetWeaver Security Guide, choose Operating System and Database Platform Security Guides. For a complete list of the available SAP Security Guides, see service.sap.com/securityguide on the SAP Service Marketplace. April

8 Components of SAP NetWeaver MDM Users 1 Components of SAP NetWeaver MDM For a complete list of SAP NetWeaver MDM components, see SAP Service Marketplace at service.sap.com/installmdm71 Master Guide. April

9 Users, Roles and Authentication Users 2 Users, Roles and Authentication MDM provides its own user management. There are no user and role features delivered on top of the MDM user management. 2.1 Users You can set passwords for MDM Servers and users of MDM repositories. Master Data Servers By default access to new Master Data Servers is not limited. You have to set a password to control access. When mounting a Master Data Server for the first time using the MDM Console, make sure that you set a password for the server. To set a Master Data Server password for the first time or to change it, select the MDM Server in the left window pane and choose MDM Servers Change Password. MDM Repositories You access MDM repositories with a user and password. SAP NetWeaver MDM uses its own mechanisms to define users. You have to set passwords for the users to control access: When creating a new repository, make sure that you set a password for the predefined Administrator user. When updating an existing repository or unarchiving a shipped repository template, you have to use the users and passwords that were already defined for the repository. Starting with MDM 7.1, you must log onto the repository at least once during an MDM Console session. This means that you have to log onto a repository each time you start the MDM Console. The icon next to the repository name indicates that you have to log onto the repository. For more information about updating repositories, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Upgrade Guide Update Repository. 2.2 Roles and Authorizations SAP NetWeaver MDM uses its own mechanisms for roles and authorizations. For more information, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 10: MDM System Administration MDM User and Role Management Roles Roles are assigned to users. Each repository contains the following standard roles: Admin and Default. They cannot be deleted. The Admin role cannot be changed. The Default role is predefined with full privileges Authorizations Authorizations (called privileges in MDM) are assigned to roles and are edited in the roles table. You can granularly enable/disable authorizations for specific functions (such as Add Records or Delete Records) or limit access to tables and fields (such as read/write access and constraints). April

10 Users, Roles and Authentication Predefined Users, Roles and Passwords 2.3 Predefined Users, Roles and Passwords In general there are one predefined user and two predefined roles when creating a repository from scratch. The predefined user is the Admin user. The Admin role is assigned to it. A password is not maintained initially for this user. It is very important to maintain a strong password for this user shortly after creating the repository. The other predefined role is the Default role. Initially it has full privileges. It is important to reduce these privileges shortly after creating the repository. 2.4 Single Sign-On Support SAP NetWeaver MDM 7.1 does not support single sign-on. When a client application is used, user IDs and passwords need to be provided to log onto the Master Data Server and the repositories. The.NET and Java APIs use the user name and password or the trusted connection concept to log onto the Master Data Server and the repositories. For more information about trusted connections, see Trusted Connection below. The ABAP API uses the trusted connection concept and extends this concept by always logging on with the sy-uname of the logged on user on the AS ABAP. 2.5 Authentication and SSO-like Feature in MDM Java Components When using the Web Services Generator or iviews, you can use an SSO-like feature. With the SSO-like feature in MDM, there is no need to re-authenticate between the application running on the SAP NetWeaver Application Server Java (AS Java) and MDS. The same MDM session is kept for different requests to the MDS issued by the same source. The AS Java object for the SSO is the SAP logon ticket. As SAP logon ticket evaluation is not currently supported in the MDS, the SSO-like feature is implemented in the MDM applications on the AS Java User Management For the SSO-like feature, the user authenticated for SAP NetWeaver Application Server Java (AS Java) should be propagated to MDM. You can do this with the following user configurations: Same users in UME and MDS: LDAP User replication in both systems Different users in UME and MDS: User mapping to an MDM system using SAP NetWeaver Portal User mapping to an MDM service user (constant user) Trusted Connection Trusted Connection configuration has direct influence on how authentication is performed and whether or not the SSO-like feature is supported. See Authentication of Trusted Connections for more information about trusted connection configuration. April

11 Users, Roles and Authentication Authentication and SSO-like Feature in MDM Java Components iviews and UWL Authentication and the SSO-like Feature The following facets have an impact on the authentication mode and SSO-like feature support: User mapping User management Trusted connection between SAP NetWeaver Application Server Java (AS Java) and MDM. User mapping is defined for a specific MDM system: Same as in iviews and UWL in the MDM 5.5 release Likely with authenticated session Trusted connection also works No user mapping: SSO-like feature User management as described in User Management on page 4 (under Same users in UME and MDS). Trusted connection is required between AS Java and MDS MDM Web Services Generator Security The Web Services Generator application is a Web application supporting basic HTTP authentication of SAP NetWeaver Application Server Java (AS Java). MDM user credentials are inserted by the user in the Web Services Generator wizard MDM Web Services Security The Web services generated by the Web Services Generator have the following security capabilities: SSL Support The transport protocol for the generated Web services can be either SOAP over HTTP or SOAP over HTTPS. You can also specify that the transport protocol for connecting generated Web services to the Master Data Server has a secure connection Authentication You can define the following authentication modes in the SAP NetWeaver Application Server Java (AS Java) for the generated Web services: No Authentication An MDM constant user is defined in the Visual Administrator/Services/Configuration Adapter and its MDM password is stored there Basic Authentication User name and password of the Web service user are propagated to MDM. This requires user management as described in User Management on page 4, under the Same users in UME and MDS section. April

12 Users, Roles and Authentication Password Change Enforcement Basic Authentication with SAP Logon Ticket SAP logon ticket support as well as basic authentication can be enabled for the Web service. User Management (as described in User Management on page 4, under the Same users in UME and MDS section) and a trusted connection between AS Java and MDS are required. 2.6 Password Change Enforcement Users with the appropriate authorization (such as the Admin role) can create new users in the MDM Console. The end user can be forced to change the password after the first logon to the Master Data Server using one of the MDM client applications. This feature prevents the administrator from knowing the passwords of the end users. You can configure this initial password behavior. The flag User Must Change Password in the MDM Console User Detail pane activates the described function if it is set to Yes. This feature can also be used by the administrator to enforce a password change by the user at any time. After creating a user, the default setting for the initial password behavior is No. You must set it to Yes after user creation. 2.7 Minimum Length of Password The minimum length of passwords can be customized. You can maintain it centrally in the mds.ini file located in the server directory...\sap\maf\mdsxx\config. One parameter is used for this setting: Minimal Password Length=5 This option sets the minimal password length (here 5 tokens). It is important to assign a strong and secure default password to each created user. After you change the minimal password length in the ini file, this password length is not automatically applied to all users whose assigned password is shorter than the minimal password length. The default value for the minimal password length is 5. It can be set to zero, but we do not recommend that you allow users without passwords. April

13 Users, Roles and Authentication Password Validity Timeframe Changes to mds.ini only take effect after a restart of the Master Data Server. Direct changes to the mds.ini file are not logged by the MDM system and it is therefore advisable to limit access to this file. 2.8 Password Validity Timeframe Users are forced to change the password after the validity timeframe for the password has expired. The validity timeframe of the password is maintained centrally in the mds.ini file located in the server directory..\sap\maf\mds{instance number}\config. Two parameters are used for this setting: Password Expiration Days=90 This option sets the time until a password will expire (here 90 days). Password Expiration Warning=7 This option sets the number of days a user will get warnings before his password expires (here 7 days). After the defined number of warnings, the user cannot log onto the system without changing his or her password. It is possible to define that the password for a user will never expire. The flag Password Never Expires in the console user administration activates the described behavior if it is set to yes. Changes to mds.ini only take effect after a restart of the Master Data Server. Direct changes to the mds.ini file are not logged by the MDM system and it is therefore advisable to limit access to this file. April

14 Users, Roles and Authentication Strong and Secure Passwords 2.9 Strong and Secure Passwords Passwords that are easily guessed (for example, with a dictionary attack, UserID, company name) are not recognized and are prevented by the Master Data Server. Users of the MDM clients should choose strong and secure passwords. Strong and secure passwords are a combination of upper and lowercase letters, numbers and special characters with a length of approximately tokens. Passwords using personal information like names or dates, user names or repetitions, dictionary words and sequences should not be used Deactivating Authorization Credentials Authentication credentials are not automatically deactivated if they have not been used for a certain period of time. The administrator should deactivate user accounts that are not in use by assigning a non-authorized role and/or by assigning a secret password Password History No history is stored for the passwords of a user. The user is not prevented from changing his or her password to a previous password. When changing their password, users of the MDM clients should choose a password that was not yet used Locking User Accounts The user account is locked after a defined number of failed password logon attempts for a defined length of time. The user account lock settings is maintained centrally in the mds.ini file located in the server directory...\sap\maf\mds00\config. Two parameters are used for this setting: Lock Account After Failed Password Attempts=3 This option sets the number of failed password logon attempts allowed before the user account is locked (here 2 attempts; with the third attempt the account will already be locked). Lock Account Duration=1800 This option sets the duration of the password lock after the failed password attempts allowed (here 1800 seconds). After the defined number of failed password logon attempts, the user cannot log onto the system for the defined number of seconds. The administrator can reset a locked account at any time. The flag Reset Account Lock in the console user administration deactivates the lock if it is set to yes. April

15 Users, Roles and Authentication CLIX Commands for Managing Passwords This feature can significantly slow down password brute force attacks if the number of allowed failed password attempts is set to a low value and the lock duration is set to a relatively high value. The User Account Lock feature does NOT work for users with the Admin role. This prevents administrators from lock out scenarios. Keep the number of users with the Admin role as small as possible. Use especially strong passwords for those users, as they are not protected against brute force attacks. Changes to mds.ini only take effect after a restart of the Master Data Server. Direct changes to the mds.ini file are not logged by the MDM system and it is therefore advisable to limit access to this file CLIX Commands for Managing Passwords The repuser set of MDM CLIX commands enable administrators to get information about, change, expire, and unexpire passwords for repository users. For complete information about these commands, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 14: CLIX Command Line Interface CLIX Commands User Administration Tools SAP NetWeaver MDM uses its own mechanism to define users. The table below shows the tools used for user management and user administration with the business scenario. Tool DBMS MDM Console Java/.NET/ABAP APIs MDM CLIX Detailed Description Use the user management of your DBMS. Use the user management as described in the MDM Console Reference Guide. In the MDM Console you define the MDM user. All available APIs offer functions for user management. You can build your own user management tools on top of the APIs. The repuser set of MDM CLIX commands enable administrators to get information about, change, expire, and unexpire passwords for repository users Standard User The table below shows the standard user created by the system when you build a repository from scratch. April

16 Users, Roles and Authentication Emergency User Concept Standard User System User ID Password Description MDM Repository Admin sapmdm MDM 7.1 Installation Guide MDM 7.1 Console Reference Guide 2.15 Emergency User Concept The emergency user concept defines how to access a system in case of loss of all administrative user credentials. To create a new password for the Admin user of an MDM repository, use the CLIX command repemergencyadminusersetpassword. For complete information about this command, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 14: CLIX Command Line Interface CLIX Commands LDAP Support Some MDM customers require support for LDAP (Lightweight Directory Access Protocol) within the MDM system. This section discusses the various issues of LDAP use within MDM What is LDAP? Simply put, LDAP is a sort of database that allows a company to control, configure and distribute user privileges, rights, and access from a single location. Without LDAP, the system manager is forced to maintain familiarity with the proprietary access control mechanism offered by each software product, and to use each one to separately maintain access control information every time an employee is hired, moves, changes job within the organization, and so on. Imagine a company with thousands of employees and dozens of programs requiring access control, and it becomes clear how much of a burden it can be to manage access control without LDAP. By contrast, by using MDM in conjunction with LDAP, MDM customers can manage access control information in a single location with a common, familiar interface of their choosing How LDAP Works LDAP acts as a lookup into a directory, very similar to using a telephone book. For example, you can perform a general search, such as one that returns all instances of Mary Lamb. In BigFoot, this returns 100+ records in the United States. Or you can restrict the search by adding in California to the search, which then returns 6 records. It turns out that the BigFoot search engine is based on an LDAP directory that includes Name and State lookup categories. Owners of LDAP directories can retrieve additional fields, categories, or attributes, such as Telephone Numbers, Primary Automobile, Hair Color, or MDM User Type. This additional information can be used as well for additional selection criteria. For MDM to support LDAP, SAP has designated the information that MDM will be querying from and that must be entered and maintained within the customer s LDAP database/directory. April

17 Users, Roles and Authentication LDAP Support Basic MDM LDAP Using LDAP within MDM conforms to the following guidelines: The customer is responsible for the maintenance and design of their LDAP directory. They must inform MDM of several LDAP directory fields and attributes so that MDM can properly search for user information. Unless an existing field is used, the customer must create one attribute field (named as desired) for MDM use. The MDM software adds no records to the LDAP directory, nor does it otherwise manage or make any design changes to its structure. It only performs lookups from the LDAP directory to read its contents. Single sign-on is not supported. Instead, MDM client software prompts the user for name and password. It was done this way for simplicity, interoperability with UNIX systems, and flexibility with various client programs or network configurations such as VPNs. MDM supports either LDAP users or MDM users, but not both simultaneously. MDM does not support connections to multiple LDAP directories MDM LDAP Fields The MDM LDAP fields are defined or created and then populated by the customer in the customer s LDAP directory. Presently, MDM makes us of LDAP user group assignments, stored in LDAP fields. In rare cases when LDAP user group assignments cannot be used, MDM requires the addition of only one attribute field (unless an existing field is used): MDMRoles a list of role names separated by semi-colons (;) While SAP suggests the name MDMRoles, you are free to choose any name that suits your situation. Since LDAP can allow multiple instances of an attribute, MDM will concatenate multiple entries as though they were in a single record separated by semi-colons (;) LDAP Access All LDAP access is performed by the Master Data Server. Clients of the Master Data Server provide MDMUserName/MDMUserPass values, which MDM then validates with LDAP. LDAP contact information and other parameters relevant to MDM are maintained in the secure mds.ini file in a separate section named: [MDM LDAP] If this section is absent, then LDAP use is disabled. Parameter Listening Mode Secure Connection to Active Directory Description Specifies if the Master Data Server accepts unencrypted, encrypted, or both types of connections. Options are Unencrypted, SSL, or Both. Specifies if the Master Data Server connects securely to the Microsoft Active Directory LDAP server. Options are True or False. April

18 Users, Roles and Authentication LDAP Support Parameter LDAP in Use Server Server Port Admin DN Admin Password Base DN User Identifier MDM Roles Attribute MDM Attribute Fallback in Use Group Identifier Member Attribute Page Size User Filter Description Whether or not MDM should use LDAP. Options are True or False. LDAP system address (usually a DNS name). The LDAP Server specification can be either a hostname or an IP address to which MDM attempts to bind; optional Server Port defaults to 389. The full DN and password of an Admin that can search for the user s full DN. For downward compatibility with previous releases MDM will construct a missing Admin DN from the following settings: Admin Identifier, Admin Name and Base DN. MDM does not need to be an administrative user to browse the directory. Just leave both Admin DN and Admin Password blank if directory setting allows anonymous binding. Any other lookup information, such as a base DN suffix, which can be used to distinguish this branch from others that the search should exclude (e.g. o=sap,c=us). It can also include information that differentiates one MDM instance from other MDM instances. The name of the LDAP id field which will match the value the user provides as the Username at logon. This would typically be something like cn or uid. The name of the LDAP attribute that will hold the group assignments, typically something like memberof. The name of the LDAP attribute that holds addresses that are assigned to users and is required for workflow. Usually this attribute is mail. Whether or not MDM should use fallback methods to provide temporary, read-only access when connection to the LDAP server is interrupted. Options are True or False. The name of the LDAP field which identifies groups. This is typically something like cn or samaccountname. This field is mandatory for Group Mapping algorithms. See MDM role algorithm below. The name of the LDAP field that lists all members of an LDAP group, like member. This field is optional. It is used for instance with LDAP server IBM Tivoli, See MDM role algorithm below. The number of records sent by the LDAP server per page. Default is This need not be changed unless the LDAP server setting differs. Optional. Limits the users search result to LDAP user entries only. Group Filter Optional. Limits the groups search result to LDAP group entries only. * For True/False values that have a default, the default is highlighted in bold. April

19 Users, Roles and Authentication LDAP Support All LDAP parameters except LDAP in Use can be changed in mds.ini without having to stop and restart MDS. You must run a Verify > Repair operation on all repositories mounted on a Master Data Server after changing the server s LDAP in Use parameter MDM LDAP Algorithm (Basic) If the Master Data Server is not using LDAP, it will proceed with its traditional MDM-specific user authorization. By contrast, if the Master Data Server is configured to use LDAP and is unable to find the LDAP server, it will completely prevent any access to the MDM system, unless fallback parameters are specified. Consider the following mds.ini example for MS Active Directory: [MDM LDAP] LDAP in Use=True Server= Server Port=389 Base DN=o=sap,c=US Admin DN=Manager,o=sap,c=US Admin Password=secret User Identifier=samAccountName MDM Roles Attribute=memberOf Group Identifier=samAccountName MDM Attribute=mail Fallback in Use=True With these parameters, LDAP authorization by the Master Data Server proceeds according to the following steps: 1. MDM receives a connection request from a client process which includes a UserName and UserPassword. 2. MDM binds to the LDAP Server using five parameters: LDAP_Host LDAP_Port LDAP_AdminDN LDAP_AdminPass LDAP_BaseDN This can fail if any of the parameter values are inaccurate. 3. As Admin, MDM searches for the full User DN (Distinguished Name) combining User Identifier and Base DN. Failure occurs if anything other than a single entry is retrieved. 4. MDM finds uid=username where basedn= o=sap,c=us. This returns a full DN, such as cn=joe Cat, ou=development, ou=engineering, ou=people, o=sap, c=us. 5. Using the full DN returned above, MDM derives the user MDM role assignments from the LDAP user group assignments. The LDAP group name maps almost directly to the MDM role name. MDM reads the attribute value, extracts the group name, drops the rest of the group s distinguished name and treats the group name as role name. 6. The list of role names is then compared to those in the MDM system to determine which are valid. Roles not found are assumed to be associated with another MDM repository and are ignored (if this is a result of a typo, the user will likely notice that he is unable to perform certain expected activities). April

20 Users, Roles and Authentication LDAP Support Do not worry about a role name occurring multiple times in your LDAP tree. However, for a case sensitive DBMS, such as Oracle, be sure to enter role names with the same case as stored in the MDM repository. Roles can be viewed from within MDM Console. 7. MDM then attempts to bind to the LDAP server using the full user DN and the provided password. If this fails, the user is prevented from logging into MDM. This MDM LDAP algorithm applies not only in connection with Microsoft Active Directory, but also for other situations where user s groups match MDM roles. For example, for IBM Tivoli Directory Server, the proper setting will be: MDM Roles Attribute=ibm-allgroups Member Attribute=ibm-allMembers MDM LDAP Algorithm (Alternative) The MDM LDAP algorithm described above makes use of LDAP user group assignments. In some rare cases, no groups are defined in LDAP or the defined groups cannot be used. An alternative approach is to store MDM role assignments in a configurable but dedicated attribute (which may require a schema change if no other existing LDAP field can be used). The idea is to retrieve user s MDM role assignments directly from that LDAP field when a user logs on to an MDM application. The mds.ini setting for MDM role assignments retrieved from dedicated LDAP field is: MDM Roles Attribute=MDMRoles Group Identifier= The Group Identifier parameter must explicitly be set to empty to distinguish the alternative search algorithm from the basic algorithm MDM LDAP Algorithm (Fallback) When the Master Data Server is using LDAP (LDAP in Use=True) user validation can fail for several reasons, such as the LDAP Server cannot be reached or the username does not exist on that server. When Fallback in Use=True, the system tries to authenticate the user after such a failure, as follows: If the username is not validated in LDAP because either the user does not exist in LDAP, or the LDAP server is unreachable, then MDM will attempt to validate that user against the traditional, internal MDM methodology. With this method, the username (and accompanying roles) must already be defined in the particular MDM repository. This may be valuable for select usernames that you wish to maintain in MDM in addition to LDAP. This kind of authentication should be restricted to admin users only. It should be used for testing or emergency only, like LDAP server downtime Although MDIS and MDSS could log-on on behalf of a repository Admin user if the fallback option was set, it's recommended to create technical users in the LDAP user directory for this purpose. April

21 Users, Roles and Authentication LDAP Support MDM Architecture in LDAP Making MDM LDAP-aware includes the following: Inspect or configure the mds.ini file to determine whether MDM uses proprietary user validation or LDAP validation. Run a Verify > Repair operation on all repositories mounted on a Master Data Server after configuring the mds.ini file for LDAP validation. If using an LDAP viewer, perform security validation and retrieve role information from LDAP as outlined in the previous sections. Use the role names retrieved from LDAP rather than the MDM repository to initialize the user and login. Any roles that are not found in the current MDM repository are ignored, and if none of the roles in the LDAP list are found, the user is prevented from logging in. Role names within MDM cannot contain semi-colons (;) nor start with an exclamation point (!), as enforced by MDM Console. The MDM administrator must design a role-naming scheme to suit the particulars of the MDM installation/implementation. If there is more than one MDM repository (such as test and development repositories, subset repositories, and so on), these will all share the role names that are stored in LDAP. While roles are designed and named via the MDM software, they are assigned to users via LDAP, centralizing this information outside of specific MDM repositories. For multi-repository environments, you may need to name roles in an MDM repository keeping in mind other repositories that could use the same role names. By having unique roles across all repositories, you can effectively control specific repository access to your users Restrictions and Limitations MDM Console users do not run under LDAP in the initial release of this functionality. We will review the value of putting MDM Console access under LDAP control at some future time LDAP Errors and MDM Errors that occur due to LDAP failures are returned to the client application. Therefore, you are likely to receive reports from clients when there are problems with your LDAP service. You should always test changes to LDAP with the MDM client software that you use. Some of the more common error messages are listed below. Error Ambiguous User Explanation / Possible Reasons More than one user exists with this login name. User Authorization Failed User exists, wrong password given. April

22 Users, Roles and Authentication LDAP Support Error Admin Authorization Failed Invalid User Unable to Initialize LDAP Host Mds.ini Problem User Has No Roles Explanation / Possible Reasons Invalid Admin DN or password setting in mds.ini. Invalid Admin Identifier setting in mds.ini. Invalid Base DN setting in mds.ini. User does not exist in LDAP. Invalid User Identifier setting in mds.ini. Server or port specified in mds.ini could not be reached. A required parameter is missing from the [MDM LDAP] section of mds.ini. Check the Master Data Server log for the missing parameter name. None of the roles retrieved from LDAP are valid for this repository. Invalid MDM Roles Attribute setting in mds.ini. April

23 Network and Communication Security LDAP Support 3 Network and Communication Security Your network infrastructure is extremely important for protecting your system. Your network needs to support the communication necessary for your business without allowing unauthorized access. A well-defined network topology can eliminate many security threats caused by software errors (at both operating system and application level) or network attacks such as eavesdropping. If users cannot log onto your application or database servers at operating system or database layer, then there is no way for intruders to compromise the machines and gain access to the database or files of the backend system. Additionally, if users are not able to connect to the server LAN (local area network), they cannot exploit wellknown bugs and security holes in network services on the server machines. The network topology for SAP NetWeaver MDM 7.1 is based on the topology used by the SAP NetWeaver platform. Therefore, the security guidelines and recommendations described in the SAP NetWeaver Security Guide also apply to the business scenario. Details that specifically apply to the business scenario are described in the following topics: Communication Channel Security As communication channels transfer all kinds of business data, they should be protected against unauthorized access. Network Security A minimum security requirement for your network infrastructure is the use of a firewall for all the services you provide in the Internet. A more secure method is to protect your systems (or groups of systems) by placing the "groups" in different network segments, each protected with a firewall against unauthorized access. External security attacks can also come from "inside", for example through social engineering. Communication Destinations Communication destinations within a SAP NetWeaver MDM installation have to be monitored. The kind of monitoring depends greatly on the implemented system landscape. Carelessly handled users and authorizations for connection destinations can cause severe security issues. Golden rules for connection users and authorizations: Assign users only the minimum authorizations required. Choose a strong default password for new users. Users should choose secure and secret passwords, and change the default password after the first logon. April

24 Network and Communication Security Securing Communication Channels Using SSL 3.1 Securing Communication Channels Using SSL Transport layer security for communication among MDM servers and clients is available using the Internet standard protocol Secure Sockets Layer (SSL). This optional encrypted channel runs alongside the existing MDM client-server TCP communication layer. MDM servers can be configured to allow clients to establish either unencrypted or secure SSL connections, and can handle both types of connections in parallel. Setting up secure communications within an MDM landscape involves the following steps: 1. Installing or upgrading MDM servers and clients to MDM 7.1 SP07 2. Configuring MDM servers for SSL. 3. Copying SSL library and client key files to client locations. 4. Creating secure connections from rich client UIs 5. Creating secure connections via APIs MDM supports SSL for communication between MDM components only. Communications established between third party applications and MDM components, including, but not limited to the DBMS, are not affected by MDM security settings; however, the third party applications may provide their own form of communication security. For more information about which MDM components support SSL-based communication, see SAP Service Marketplace at service.sap.com/installmdm71 Master Guide Securing Communication Channels Using Secure Sockets Layer (SSL). 3.2 Secure Connection Prerequisites All MDM servers and clients must be version 7.1 SP07 or higher. In addition, the following server-side and client-side components are required in order to establish secure connections on MDM systems. MDM server-side components: SSL Library file: sapcrypto.dll Key file: SAPSSLS.PSE Ticket file: ticket MDM client-side components: SSL Library file: sapcrypto.dll Key file: CLIENT.PSE Ticket file: ticket Key files and ticket files are created automatically during the installation/upgrade process, but the SSL Library file must be downloaded separately. For information about downloading the SSL Library file, see SAP Note The ticket file must be located in the same directory as the SSL Library file. Rich UI clients such as MDM Console, MDM Data Manager, MDM Syndicator, and MDM Import Manager require the 32-bit version of the SSL Library file. April

25 Network and Communication Security Configuring MDM Servers for SSL 3.3 Configuring MDM Servers for SSL Server-side SSL settings are stored in a server s.ini file. For information about configuring MDM server parameters, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 7: MDS Administration. If you are upgrading from a version of MDM prior to MDM 7.1 SP07, the parameters described in this section must be manually added to your server configuration files. They are added automatically only for new installations of MDM 7.1 SP MDS Configuration The following Master Data Server (MDS) settings are stored under the [MDM Server] section of the mds.ini file. Parameter Listening Mode SSL Lib Path SSL Key Path Description Specifies if the Master Data Server accepts unencrypted, encrypted, or both types of connections. Options are Unencrypted, SSL, or Both. The path to the server s SSL Library file. The path to the server s SAPSSLS.PSE file If the Listening Mode parameter is set to Unencrypted, attempts by clients to establish secure connections to the Master Data Server will fail Auxiliary and Slave Server Configuration The following auxiliary server (MDIS, MDSS, MDLS) settings are stored in mdis.ini, mdss.ini, and mdls.ini under the header: [MDM Server\Remote Server\<MDSHOST>:portNumber] where <MDSHOST> is the name of the machine on which the MDS is installed and portnumber is the listening port for the specified MDS (for example, myhost:50051). Parameter Service Control Security Enabled SSL Enabled SSL Lib Path SSL Key Path Description Options are True or False. Must always be False on UNIX landscape. Specifies if the server connects to MDS on an unencrypted or SSL port. Options are True or False. For the server to establish a secure connection to MDS, this parameter must be set to True. The path to the auxiliary server s SSL Library file. The path to the auxiliary server s SAPSSLS.PSE file The <MDSHOST>:portNumber value in the Remote Server heading must exactly match the Server value located under the [GLOBAL] heading in the auxiliary server s.ini file. April

26 Network and Communication Security Connecting Securely from MDM Clients The header and parameters described in this section must also be added to the mds.ini file of any remote MDS on which a slave repository is mounted. For more information, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 7: MDS Administration SSL-Specific Parameters for a Client MDS. 3.4 Connecting Securely from MDM Clients Connecting Securely from MDM Console Icons in the Console Hierarchy tree display locks to indicate a secure connection to a SSLenabled server was established when the server was mounted on the Console. Secure connections to SSL-enabled MDM servers must be configured from within an MDM Console. For more information, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 7: MDS Administration Accessing Master Data Servers Connecting Securely from other Rich Clients When connecting MDM Data Manager, MDM Import Manager, MDM Syndicator, or MDM Publisher to a repository on an SSL-enabled Master Data Server, a lock icon appears on the client s Connect To MDM Repository dialog. Secure connections to repositories on SSL-enabled MDM servers must be configured from within each client. For information, see Setting Up Secure Repository Connections in the client s reference guide. April

27 Network and Communication Security Connecting Securely from MDM Clients Connecting Securely from MDM CLIX Before you can connect CLIX to an SSL-enabled Master Data Server, you must add the paths to the client-side SSL library and key files to the clix.ini file. Adding the Y[+] option flag to a CLIX command then encrypts communication with the MDS. For more information, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Console Reference Guide Part 14: CLIX Command Line Interface Connecting Securely from MDM APIs For information about establishing SSL secure connections from applications that use MDM Java or.net APIs, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Java and.net API : Getting Started with Java API Tasks Managing Connections and Sessions For information about establishing SSL secure connections from ABAP API applications, see SAP Service Marketplace at service.sap.com/installmdm71 MDM ABAP API Configuring MDM ABAP API for SNC Connecting Securely from MDM Web UIs For information about establishing SSL secure connections from Web UIs, see SAP Service Marketplace at service.sap.com/installmdm71 : MDM Portal Content Development Guide Connecting with the MDM Repository Configuring a System Object MDM Web Dynpro Components Guide Installing the MDM Web Dynpro Environment Creating a Destination for the MDM Repository Connecting Securely from MDM Web Services For information about establishing SSL secure connections from Web UIs, see SAP Service Marketplace at service.sap.com/installmdm71 MDM Web Services Guide : MDM Web Services Generator (Design Time) Generating a New Web Service Generated Web Services (Runtime) Creating MDM Destinations for Web Service Operation Calls Generated Web Services (Runtime) Installing MDM Web Services Runtime Environment MDM Web Services Security Generated Web Services (Runtime) Data Types Common Data Types Generic Data Types RepositoryInformation Data Type Generated Web Services (Runtime) Web Services and Operations Generic Functionality for Web Service Operations Connecting the MDM Repository at Runtime Connecting Securely from MDM PI Adaptor For information about establishing SSL secure connections from the MDM PI Adaptor, see SAP Service Marketplace at service.sap.com/installmdm71 MDM PI Adapter Guide Setting Up Messaging MDM Adapter Specific Configuration. April