SAP Single Sign-On 2.0: Overview Presentation
SAP Single Sign-On 2.0: Overview Presentation
SAP Single Sign-On 2.0: Overview Presentation
0
Overview Presentation
July 2015 Public
Agenda
SAP
Business Suite
SAP Cloud
Applications Authentication and Governance Risk Identity Enterprise Threat
Single Sign-On and Compliance Management Detection
SAP Mobile
Applications
3rd Party Make it simple for your users to Ensure corporate compliance to Making sure you know your Making sure to counter possible
do what theyre allowed to do. regulatory requirements. users and what they can do. threats and identify attacks.
Systems
70 70
Faster onboarding Reduction of password
of new hires related help desk calls
% %
Manage identity lifecycle Single sign-on Apps Find Detect cyber User mgmt
Segregation of duties Secure network communication Devices vulnerabilities in crime attacks Connectivity
Emergency access Central access policies Content customer code based on user Authentication
Role management 2-factor authentication behavior Encryption
Risk mgmt
Digital Sigs
Reporting Ent. App
WS Security
Store
Security
Reduce Costs
Simplicity
2015 SAP SE or an SAP affiliate company. All rights reserved. Public 8
SAP Single Sign-On Benefits in Detail
Security
With just one password to remember, a strong password policy is finally feasible
No more need for password reminders on post-its
All passwords kept in one protected, central place
Reduce Costs
Efficiency gains for users that only need to remember one password
Higher productivity due to reduced efforts for manual authentication, password reset,
helpdesk interaction,
Simplicity
Lean product, fast implementation project, quick ROI
No more efforts to provision, protect and reset passwords across many systems
No more efforts to manage password policies across many systems
SAP Single Sign-On provides a simple and secure access to IT applications for business users, encrypts company
data and provides optionally advanced security to protect important business applications.
Simple and secure access
Single sign-on for native SAP clients and web applications
Single sign-on for mobile devices
Support for cloud and on-premise landscapes
Microsoft Active
SAP Business Suite Directory
Token: Kerberos
SPNEGO only
available in newer
SAP NetWeaver
releases
SAP NetWeaver
Microsoft Active
SAP Business Suite
Directory, LDAP,
other login modules
Token: X.509
certificate
NW AS JAVA
Multiple ways of user credential
1 User Desktop verification (SPNEGO, LDAP,
HTTPS SAP NetWeaver
AS Java ABAP, UME,...)
6 Single Sign-On and Secure Login Server requires
Secure Communication AS Java
Microsoft Active
Directory, LDAP,
other login modules
Cloud applications
Token: SAML
SAML is a public
standard for Web
Web client applications. The
SAP / non-SAP application server has
Web applications to support the
standard.
Recommended for
extranet scenarios,
partner integration
Authentication
Server In a Nutshell
2
Relies on Security Assertion
Client Authenticate SAP NetWeaver Markup Language (SAML)
AS Java assertions as security token
Identity Provider 3 Industry standard for cloud
Browser
4 Return SAML (IdP)
Verify User and cross-company scenarios
Assertion
Credentials Assertions created by Identity
Provider, running on AS Java
Authentication initiated by
HTTPS Service Provider
Service
IdP or SP
(SP) (SP)
Provider Multiple ways of user
credential verification
(SPNEGO, LDAP,
HTTPS ABAP, UME,..)
1 User Desktop Service
Service Provider
Provider
(SP) (SP)
5 Single Sign-On and
Secure Communication
Identity Provider
Central service on SAP NetWeaver AS Java
Provides SAML 2.0 assertions for Web-based SSO
Component SAP NW SSO 2.0 Secure Login Library Crypto Kernel was certified on January 6th, 2015
Certificate:
http://csrc.nist.gov/groups/STM/cmvp/document
s/140-
1/140crt/FIPS140ConsolidatedCertList0049.pdf
Usage Scenarios
Recommended for scenarios with particular security
requirements
Web and SAP GUI applications
Risk-Based Authentication
Risk-based enforcement of stronger authentication
Example: User accesses from outside the corporate network 2FA (two-factor authentication) is required
Details
Relies on time-based One-Time Passwords for
authentication
SAP Authenticator apps available for iOS and Android
End user self registration user interface
Administrative user interfaces
Usage Scenarios
Single sign-on for web applications
Single sign-on for customized Fiori native client (see
SCN blog for details)
Usage Scenarios
Warehouse and production scenarios
Kiosk/terminal computers
Recent Enhancements
Simplified configuration based on Microsoft Active Directory
Support for additional RFID reader devices
Situation
It is often a compliance requirement to only allow encrypted communication to SAP systems
As documented in SAP Note 1690662, unencrypted communication can be blocked
Enabling this setting may be a risk for business continuity if SAP Single Sign-On was not yet configured
on all clients, as some people may lose access to the system
Solution
Unencrypted access to the backend can be recorded in the Security Audit Log, as documented in SAP
Note 2122578
Customers can enable the logging function and keep an eye on whether there are still unencrypted
connections from certain client machines, which can then be configured to use SAP Single Sign-On
Once the administrator is reassured that there are no more clients with missing configuration out there,
she can enforce encrypted communication as described in SAP Note 1690662
Thales SafeNet
Cloud and
cross-company
SAP
Business Suite
Identify the most critical systems. Which systems contain your most sensitive business information?
How many people have access to them? Define your overall single sign-on strategy and start with
these critical business systems.
Understand the different modules of SAP Single Sign-On and analyze your system landscape to
determine which SSO standards can be used. If your organization does not have the appropriate
resources and know-how, involve SAP Consulting or SAP partners.
Passwords are often the weakest link in enterprises. Prevent the usage of passwords by relying on
standards such as SAML, X.509 certificates, or Kerberos. SAP Single Sign-On offers solutions for
all of these standards.
Once you have implemented single sign-on, start enforcing strong passwords in the related systems.
Mid-term strategy: Consider disabling user name/password authentication in critical business
systems.
It offers
Investment protection
Flexibility
Single sign-on for heterogeneous system landscapes
Community Network
http://scn.sap.com/community/sso
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.