Single Sign on for SAP Netweaver Application Server (ABAP) On
Total Page:16
File Type:pdf, Size:1020Kb
Single Sign On for SAP NetWeaver Application Server (ABAP) on Power Systems How to enable Single Sign On with Secure Network Communication using Kerberos on SAP Application Servers (ABAP) running on Power Linux or AIX with a central Active Directory serving as Kerberos server Cäcilie Hampel ODOE Technology & Solutions Development Oktober 2009 This document can be found on the web, www.ibm.com/support/techdocs © Copyright IBM Corporation, 2009. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders Table of contents Abstract ................................................... ................................................... ........................... 3 Preface ................................................... ................................................... ........................... 3 Kerberos Client Configuration ................................................... ......................................... 5 a.) Novell Linux Kerberos Client Configuration ................................................... ................................ 5 b.) Red Hat Linux Kerberos Client Configuration ................................................... ............................ 6 c.) AIX Kerberos Client Configuration ................................................... .............................................. 8 Add Linux/AIX Server as host to Active Directory and create keytab .............................. 9 a.) Initialize keytab on Linux host ................................................... ................................................... 10 b.) Initialize keytab on AIX host ................................................... ................................................... .. 11 Enable SAP NetWeaver Application Server (ABAP) for SNC .......................................... 11 Enable SAP user for SNC ................................................... ................................................ 13 Enable Kerberos and SNC on Windows Client ................................................... ............. 15 Testing SSO ................................................... ................................................... .................. 18 Error detection/Known problems ................................................... ................................... 19 Links and Resources ................................................... ................................................... ... 20 Products used in this paper ................................................... ........................................... 21 About the author ................................................... ................................................... ........... 21 Acknowledgements ................................................... ................................................... ...... 21 Trademarks and special notices ................................................... .................................... 22 Single Sign On (SSO) with Kerberos for SAP on Power Linux and AIX 2 © Copyright IBM Corporation, 2009. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders Abstract The system landscape of companies grows rapidly. At the same time, the number of users increases as in heterogeneous system landscapes one employee often uses several user IDs for different systems. This leads to high maintenance and support effort as well as higher total cost of ownership and security risks. A possible solution to this situation could be Single Sign On (SSO). The name already tells all about SSO: the user has to sign on only once. This means he must remember only one user name and one password. This paper describes the setup of SSO for SAP® NetWeaver™ Application Server based on the Kerberos™ protocol. It makes use of the common combination of Windows® workstations grouped in a Microsoft® Active Directory™ domain and SAP on Linux® and AIX® running on IBM® Power™ Systems. Preface SAP offers Secure Network Communication (SNC) as a component to integrate an external security product into SAP systems. In this paper, the used external security product will be Kerberos. Kerberos is a network authentication system based on a key distribution model and a central repository. The idea is that every resource authenticates itself against the Kerberos server and receives a key, also called ticket. This ticket is then used during communication with others to identify the resource as a trusted partner and enables single sign on as no passwords will be requested due to the ticket exchange. The first step for a Kerberos authenticated communication is that a resource authenticates itself against a Kerberos authentication server and requests a ticket. This first ticket is the Ticket Granting Ticket (TGT) that is used for the communication with the Kerberos Key Distribution Center (KDC). Further, during the first communication with the authentication server, a session key is created that can be used for encrypted communication. The Kerberos authentication server and the KDC are two independent servers and could work on different servers but usually, they are part of the same system and are seen as an unit. When the resource now tries to connect to another party, it needs another ticket. Therefore it sends the TGT and a ticket request to the KDC that creates tickets for the communication with other Kerberos enabled resources. The KDC will respond with a ticket for the communication between the two partners. The first resource forwards the ticket to the host with which it would like to communicate. If the host accepts the ticket as valid, the resource has been authorized to connect to the system for the duration of the ticket. The tickets have a limited lifetime and must be renewed after a while, normally after eight to ten hours. Another security setting is that every ticket is also bound to a unique SPN, Service Principal Name, that clearly identifies a user or resource. The ticket can only be used by the partner to which it was granted. Single Sign On (SSO) with Kerberos for SAP on Power Linux and AIX 3 © Copyright IBM Corporation, 2009. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders Kerberos AuthenticationServer 1. Authentication Request 2. Ticket Granting Ticket 3. Ticket Granting Ticket Key Partner 1 Distribution (e.g. Windows Center Workstation) 4. Ticket (for communication with Partner 2) 5. Ticket er on his local workstation, the active directory that serves as a tion server and the KDC. soft Active directory domain is beros server during log on. Apart ion Programming Interface (GSS- Partner 2 s SNCe Linux/AIXuses the GSS-API host; it needs interface also (e.g. SAP System) be registered as domain user. ive directory users section. As will activelye started authenticate once and then it against run on its In the SAP context, the involved parties are the us - we will use another mechanism. SAP system on a Linux or AIX host, and the central ated that holds the credentials of Kerberos server, which contains both the authentica computer account. This keytab is The user on his workstation that is part of a Micro l user and all applications running automatically authenticated against the central Ker tication. As the SAP system is from that only a Generic Security Services Applicat ust be authorized to call the API) library must be installed on the workstation a to communicate with Kerberos. The same refers to th thenticated against the Kerberos the GSS-API lib. ded for communication with other Further, also the host the SAP systems runs on must started by different users, there Therefore, a computer account is created in the act Linux and AIXved. there will not be a physical user on the host that the Kerberos server – in fact the SAP system will b own without direct interaction by an administrator On the active directory server, a keytab can be cre the host, as well as its encrypted password of the erein are the property of their respective holders then copied to the host. It can be called by a loca under this user will be enabled for Kerberos authen running under a userid called <sid>adm, this user m keytab. Not the user itself but the host© Copyright is then IBM Corporation,au 2009. All Rights Reser server. The user will, however, hold the ticket nee parties. So, if thereSingle are Sign applications On (SSO) with onKerberos one forhost SAP on Power 4 All trademarks or registered trademarks mentioned h must be one ticket for each user. The tickets must be renewed in regular intervals. This can be done in an automated job. After SAP system host and user have authenticated themselves against the Kerberos server, the user is able log in to the SAP application without password input, the authentication is done in the background. Now, after the technical background has been described, you need to perform the following steps to enable your own SAP system for SSO: ● Kerberos Client Configuration ● Add Linux/AIX Server as host to Active Directory and create keytab ● Enable SAP NetWeaver Application Server (ABAP) for SNC ● Enable SAP User for SNC ● Enable Kerberos and SNC on Windows Client ● Testing SSO Kerberos Client Configuration To enable the Linux or AIX Server for Kerberos authentication, it needs a Kerberos client that will talk to the central Active Directory Kerberos server. Before you start with the configuration of Kerberos client,