SAP Cloud Identity Service-1
SAP Cloud Identity Service-1
2017-03-28
Table 1:
Get Started What's New
Scenarios Resources
Terms of Use
Privacy
Legal Disclosure
Disclaimer
Table 2:
Announcement
To improve the failover mechanism for Identity Authentication, we will add a new IP address (155.56.128.137) for the land
scape host in Europe. If you have whitelisted the current IP, you also need to whitelist the new IP for the corresponding
scenarios to work. For more information about Identity Authentication landscape hosts, see Landscape Host [page 15].
Table 3:
Enhancement
SAP Cloud Identity service is renamed to SAP Cloud Platform Identity Authentication service (in short, Identity
Authentication). The renaming includes changes in the following:
Table 4:
Enhancement
Updated the documentation links in the administration console for Identity Authentication. The updated links lead to the
Identity Authentication documentation in the New SAP Help Portal .
Table 5:
Enhancement
Certain configuration options for the system applications are read-only. For more information, see Configure a Trusted
Service Provider [page 35], Configure the User Attributes Sent to the Application [page 38], Configure the Name ID At
tribute Sent to the Application [page 41], Configure the Default Attributes Sent to the Application [page 43], and
Choose Identity Provider for an Application [page 73].
Enhancement
Redesigned the Log On screen of SAP Cloud Platform Identity Authentication service place, changing the place of the
Forgot password link.
Date Description
2016-12-12 ● Added search field for the master lists in the Import Users, Applications, Terms of Use Documents,
Privacy Policy Documents, and Corporate Identity Providers tiles in the administration console.
● Changed the name of the system application that contains the configurations of the Profile Page to
User Profile. For more information about the system applications, see Configure Applications [page
26].
2016-11-17 ● Extended SCIM REST API with new attributes in accordance with the Custom Attributes Schema Ex
tension. Tenant administrators at Identity Authentication can store, read, create, and update cus
tomer specific data in up to 10 custom attributes. For more information, see SCIM REST API [page
204].
● Added a warning message that appears when the tenant administrator chooses a system applica
tion for configuration in the administration console for Identity Authentication. For more information
about the application types, see Configure Applications [page 26].
2016-10-10 ● Extended the attributes that can be sent to the application in the SAML 2.0 assertion with Lan
guage, Cost Center, Department, Division, and Employee Number. For more information about
the assertion attributes, see Configure the User Attributes Sent to the Application [page 38].
2016-10-03 ● Tenant administrators can change the name format of the identity provider in the administration
console for Identity Authentication. For more information, see Tenant SAML 2.0 Configuration [page
76].
2016-09-14 ● Tenant administrators can create, configure, and set a custom password policy for scenarios where
Identity Authentication is the authenticating authority. For more information, see Configure Custom
Password Policy [page 106].
2016-08-30 ● The SAP UI5 extension Fiori for Tools is applied to the administration console for Identity
Authentication. It includes controls like Side Navigation, Tool Header, and Block Layout. Navigation
entries in the administration console have an icon, and features belonging to the same category are
grouped together.
2016-08-16 ● Identity Authentication protects the applications against clickjacking when using embedded frames
for the logon pages. For more information, see Configure Clickjacking Protection [page 250].
2016-08-05 ● Tenant administrator can change user type via the administration console for Identity
Authentication. For more information, see List and Edit User Details [page 122].
● Tenant administrator can upload terms of use and privacy policy documents, and e-mail templates
in all supported languages. For more information, see Configure Terms of Use [page 113], Config
ure Privacy Policies [page 109], and Define an E-Mail Template Set for an Application [page 61].
2016-07-18 ● Identity Authentication master data texts can be changed and updated via API. For more informa
tion, see Change Master Data Texts [page 241].
● Identity Authentication provides support for languages written in Right-To-Left (RTL) direction. For
more information about the supported languages, see Supported Languages [page 17].
2016-07-04 ● Extended the user import via CSV file with the language column. Tenant administrator can specify
the language of the user via CSV file import. The user receives the activation e-mail in that language.
For more information, see Import or Update Users for a Specific Application [page 68].
2016-06-20 ● Tenant administrator can specify a link, which can be used by the application to redirect the user
after successfully logging out of the application when Identity Authentication acts as an identity pro
vider proxy. For more information, see Configure Logout URL [page 159].
● Tenant administrator can change the user attributes taken from Microsoft Active Directory, or can
also add additional attributes that are defined in the SCIM Enterprise User Schema Extension. For
more information, see Configure SAP Cloud Platform [page 84].
2016-06-06 ● Tenant administrators can edit the E-Mail information in the administration console for Identity
Authentication. For more information, see List and Edit User Details [page 122].
● Added new attributes that are sent to the remote system in user provisioning. For more information
about the supported attributes and the mapping between Identity Authentication and SAP Jam, see
Provision Users to SAP Jam Target Systems [page 133].
2016-05-25 ● Country field in registration and upgrade form is required when Zip/Postal Code is filled in.
For more information, see Configure Registration and Upgrade Forms [page 63].
● Extended SCIM REST API with the possibility to create and update users with no password and no
activation e-mail sending. Added new attributes: sendMail, mailVerified. For more informa
tion, see SCIM REST API [page 204].
● Extended the SCIM REST API with corporateGroups attribute. For more information, see SCIM
REST API [page 204].
2016-05-10 ● Extended SCIM REST API with new attributes: employeeNumber, costCenter, organization, division,
department, manager, in accordance with the Enterprise User Schema Extension. For more infor
mation, see SCIM REST API [page 204].
● Supports Employee Number as NameID attribute. For more information, see Configure the
Name ID Attribute Sent to the Application [page 41].
● Added Italian and Welsh to the supported languages for end user screens. For more information, see
Supported Languages [page 17].
2016-04-26 ● Extended SCIM REST API with passwordStatus, userType, sourceSystem, and
socialIdentities attributes. For more information, see SCIM REST API [page 204].
● Extended the number of user attributes with a new section Employee Information in User Details
view of the administration console. For more information, see List and Edit User Details [page 122].
2016-04-11 ● The tenant texts of Identity Authentication can be changed and updated via API. For more informa
tion, see Change Tenant Texts REST API [page 235].
● You can define rules for authentication for the administration console for Identity Authentication ac
cording to different risk factors. For more information, see Configure Risk-Based Authentication
[page 51].
2016-03-31 ● Tenant administrators can check if the SAP Jam Target System is configured properly by testing the
connection. For more information, see User Provisioning [page 133].
● Tenant administrators can delete a selected target system or several target systems in a tenant of
SAP Cloud Platform Identity Authentication service. For more information, see Delete SAP Jam Tar
get System [page 140].
● Tenant administrators can search users in the administration console choosing between simple and
advanced search. For more information, see Search Users [page 120].
2016-03-20 ● Tenant administrators can delete a selected user group in a tenant of Identity Authentication. For
more information, see Delete User Groups [page 131].
2016-02-29 ● Tenant administrators can provision users to SAP Jam instances. For more information, see User
Provisioning [page 133].
● Tenant administrators can delete a selected application in a tenant of Identity Authentication. For
more information, see Delete Applications [page 33].
● Tenant administrators can delete a selected corporate identity provider in a tenant of Identity
Authentication. For more information, see Delete Corporate Identity Providers [page 164].
2016-02-15 ● Tenant administrators can assign user groups to corporate identity providers so that only users part
of these groups can access the application. For more information, see the Assign User Groups to
Corporate Identity Providers section in Configure Identity Federation with the User Store of SAP
Cloud Platform Identity Authentication Service [page 166].
2016-02-01 ● SCIM REST API implementation of Identity Authentication is updated and supports full set of attrib
utes to create, update, and delete user resources. For more information, see Create User Resource
[page 218], Update User Resource [page 226], and Delete User Resource [page 234].
● Tenant administrators can enable or disable a check if a user authenticated by a corporate identity
provider exists in the cloud user store of Identity Authentication. For more information, see the Ena
ble Identity Federation with Identity Authentication User Store section in Configure Identity Federa
tion with the User Store of SAP Cloud Platform Identity Authentication Service [page 166].
2016-01-18 ● Tenant administrators can define rules for authentication in accordance with the risk. For more in
formation, see Configure Risk-Based Authentication [page 51].
● Tenant administrators can enable or disable the reload of the application's parent page after a suc
cessful logon. For more information, see Enable or Disable Reload Parent Page Option [page 60].
● SCIM REST API implementation of Identity Authentication supports create, update, and delete of
user resources. For more information, see Create User Resource [page 218], Update User Re
source [page 226], and Delete User Resource [page 234].
Date Description
2015-12-08 ● Tenant administrators can delete one or more corporate identity providers in a tenant of Identity
Authentication. For more information, see Delete Corporate Identity Providers [page 164].
● Added a new tenant administrator's role - Manage Groups. For more details how to assign adminis
trator roles, see Edit Administrator Authorizations [page 146].
2015-11-23 ● Tenant administrators can add systems in the administration console for Identity Authentication to
act as administrators. For more information, see Add System as Administrator [page 144].
● Tenant administrators can configure the validity of the link sent to a user in the different application
processes. For more information, see Configure E-Mail Link Validity [page 78].
● Tenant administrators can edit the user details information in the administration console for Identity
Authentication. For more information, see List and Edit User Details [page 122].
2015-10-27 ● Tenant administrators can view monthly statistics on the user logons, For more information, see
View Usage Statistics [page 179].
● Added optional parameter in the User Management REST API allowing the option not to send the
activation e-mail. For more information, see User Registration Service [page 200].
● Redesigned end user interfaces providing usability improvements and fixes. The UI now works fine in
both an IFrame and when shown in full browser window. Improved responsive behavior and markup,
and refactored CSS for easier implementation and maintenance.
2015-10-12 ● Added a new tenant administrator's role - Manage Users. For more details how to assign administra
tor roles, see Edit Administrator Authorizations [page 146].
● Tenant administrators can delete one or more user groups in a tenant of Identity Authentication. For
more information, see Delete User Groups [page 131].
● Tenant administrators can change the certificate used by the identity provider to digitally sign the
messages for the applications. For more information, see Tenant SAML 2.0 Configuration [page
76].
● Tenant administrators can configure Kerberos authentication for Identity Authentication to allow
users to log on without username and password when they are in the corporate network. For more
information, see Configure Kerberos Authentication [page 95].
2015-09-28 ● Tenant administrators can Configure Trusted Domains [page 80] in the administration console for
Identity Authentication
2015-09-14 ● Users can use Remember me option to log in to applications. For more details, see Use the Remem
ber Me Option [page 189].
● Users can access applications with single sign-on on mobile devices. For more details, see Access
Applications with Single Sign-On on Mobile Devices under Use the Remember Me Option [page
189]. See also Set Mobile Single Sign-On [page 74].
● Administrators can list the users that are assigned to a given user group. For more details, see List
Users in User Groups [page 128].
2015-08-31 ● Tenant administrator can disable IdP-Initiated process on tenant level. For more information see,
Configure IdP-Initiated SSO [page 99].
● SCIM REST API implementation of Identity Authentication supports pagination and search by more
than one attribute and one attribute can be included into the filter more than one time; tenant ad
ministrator can retrieve a known user; location attribute is returned and in the search results. For
more information, see SCIM REST API [page 204].
2015-08-04 ● Tenant administrator can list user groups in the tenant. For more information, see List User Groups
[page 127].
● Tenant administrator can create new user groups via the administration console for Identity
Authentication. For More information, see Create a New User Group [page 126].
● Tenant administrator can assign or unassign groups for a user via the administration console for
Identity Authentication. For more information, see Assign Groups to a User [page 129], Unassign
Users from Groups [page 130].
● Tenant administrator can add users to user groups via the groups column in the CSV file. For more
information, see Import or Update Users for a Specific Application [page 68].
● Applications can search users by attribute via the SCIM REST API. For more information, see Users
Search [page 205].
● Tenant administrator configures the groups attribute to be sent with the SAML 2.0 assertion. For
more information, see Configure the User Attributes Sent to the Application [page 38].
2015-07-06 ● Tenant administrator creates new users in the administration console for Identity Authentication.
For more information, see Create a New User [page 119].
● Tenant administrator can configure social providers separately. For more information, see Configure
Social Identity Providers [page 169].
2015-06-22 ● When an application uses HTTP basic authentication for API calls, the password locks for 60 min af
ter 5 failed logon attempts with wrong value.
● When searching for users, the system displays the first 20 users in the tenant sorted by their user ID
number. If the users are more than 20, the list can be expanded. For more information, see Search
Users [page 120].
● Tenant administrator deletes users in the administration console for Identity Authentication For
more information, see Delete Users [page 123].
● You can now configure Identity Authentication to connect to your corporate user store to request
additional user information. That might be necessary when the information about your users is not
available in the user store of Identity Authentication. For more information, see Configure Connec
tion to a Corporate User Store [page 84].
2015-06-08 ● Administrator sets a password for HTTP basic authentication when Identity Authentication API is
used. For more information, see Configure Credentials for HTTP Basic Authentication [page 48] .
● Administrator can set custom attributes with a CSV file. For more information, see Import or Update
Users for a Specific Application [page 68].
2015-05-26 ● Identity Authentication adds additional user attributes to the standard set of user attributes on the
user registration form, in the assertion attributes configuration in the administration console, and in
the SAML 2.0 assertions. For the full list of the attributes, see Configure Registration and Upgrade
Forms [page 63].
● Application sets custom attributes via the user registration service. For more details, see User Reg
istration Service [page 200].
● Tenant administrator configures custom attributes to be sent with the SAML 2.0 assertion. For more
information, see Configure the User Attributes Sent to the Application [page 38].
Note
This functionality has been updated. Now it is part of the Risk Based Authentication. For more in
formation, see Configure Risk-Based Authentication [page 51].
● Administrator deactivates all user mobile devices that generate passcodes for applications with two-
factor authentication. For more information, see Deactivate User Devices for Two-Factor Authenti
cation [page 124].
● Administrator unlocks user passcode for two-factor authentication. For more information, see Un
lock User Passcode [page 124].
● User activates and deactivates mobile devices that generate passcodes for access to applications
with two-factor authentication. For more information, see Two-Factor Authentication [page 184],
Activate a Device for Two-Factor Authentication [page 185], Deactivate Devices Configured for Two-
Factor Authentication [page 186].
2015-03-30 ● Choose an identity provider for a specific application. The tenant administrator can choose between
the default identity provider and a corporate identity provider. For more information, see Choose
Identity Provider for an Application [page 73].
● Search, view, and list the users, and view detailed information about them in the administration con
sole for Identity Authentication. For more information, see List and Edit User Details [page 122].
2015-03-16 ● Configure trusted identity provider in the administration console for Identity Authentication. For
more information, see Configure Trust with Corporate Identity Provider [page 160].
2015-03-02 ● Delete one or more applications in a tenant of Identity Authentication. For more information, see
Delete Applications [page 33].
● Configure and visit the Home URL of an application. For more information, see Configure an Applica
tion's Home URL [page 31], Visit an Application's Web Page [page 32].
● Import or update users for an application, and send activation e-mails. For more information, see
Import or Update Users for a Specific Application [page 68].
2015-02-16 ● Edit administrators' roles in the administration console for Identity Authentication. For more infor
mation, see Edit Administrator Authorizations [page 146].
2015-02-02 ● Add users as administrators in the administration console for Identity Authentication. For more in
formation, see Add Administrators [page 143].
2015-01-19 ● List administrators in the administration console for Identity Authentication. For more information,
see List Administrators [page 142].
Date Description
2014-12-08 ● Change the tenant's display name. For more information, see Change a Tenant's Display Name
[page 81].
● Users created via CSV upload receive activation mail.
● Application specific logo. For more information, see Configure a Logo for an Application [page 55].
● Global tenant logo. For more information, see Configure a Tenant Logo [page 77].
● Configure SAML 2.0 trust by uploading metadata or by entering the service provider's information
manually. For more information, see Configure a Trusted Service Provider [page 35].
● Set up the user attributes that are sent to the application in the SAML 2.0 assertion. For more infor
mation, see Configure the User Attributes Sent to the Application [page 38].
● Configure attributes with default values for the application. For more information, see Configure the
Default Attributes Sent to the Application [page 43].
● Choose which user attributes to be on the application's registration and upgrade forms. For more
information, see Configure Registration and Upgrade Forms [page 63].
● Upload certificate for REST API authentication.
● Log on with social network accounts. For more information, see Enable or Disable Social Sign-On for
an Application [page 44], Configure Social Identity Providers [page 169].
1.2 Overview
SAP Cloud Platform Identity Authentication service is a cloud solution for identity lifecycle management for SAP
Cloud Platform applications, and optionally for on-premise applications. It provides services for authentication,
To use Identity Authentication, you must obtain a tenant. The tenant represents a single instance of the Identity
Authentication that has a specific configuration and data separation.
For configuration of most features, administrators use the administration console for Identity Authentication,
which is a Fiori-based user interface adaptive to most browsers. For more information about the administration
console, see Operation Guide [page 25].
Related Information
Authentication with user name and Users can log on to applications with Scenarios [page 20]
password their user name and password.
Single sign-on to applications on SAP Users can access multiple cloud applica Scenarios [page 20]
Cloud Platform tions in the current session by authenti
cating just once in the Identity
Authentication.
Social sign-on to applications on SAP Users can link their Identity Scenarios [page 20]Social Identity Pro
Cloud Platform Authentication account with a social net viders [page 169], Social Authentication
work account. That way users can be au [page 187].
thenticated through a social identity pro
vider.
Customized branding Administrators can configure branding Configure a Tenant Logo [page 77],
styles for UI elements, e-mails, and error Configure a Logo for an Application
pages so that they comply with the com [page 55], Configure a Branding Style
pany’s branding requirements. for an Application [page 59], Define an
E-Mail Template Set for an Application
[page 61], Configure Registration and
Upgrade Forms [page 63]
Customized privacy policy and terms of Administrators can add customized Define a Terms of Use Document for an
use management terms of use and privacy policy, which Application [page 116], Define a Privacy
users have to accept before registering. Policy Document for an Application
They are shown on the registration and [page 112].
upgrade forms.
Customer security policy Administrators can select a password Set a Password Policy for an Application
policy from a list in accordance with the [page 104]
security requirements and the rules for
resetting passwords.
Dedicated customer tenant Customers are provided with guaran Configure Tenant Settings [page 75]
teed availability and specific configura
tion of their tenants.
User import functionality Administrators can import new users Import or Update Users for a Specific
into Identity Authentication or can up Application [page 68]
date data for existing users.
User export functionality Administrators can download informa Export Existing Users of a Tenant of SAP
tion about existing users in the current Cloud Platform Identity Authentication
tenant. Service [page 177]
Detailed change logs Administrators can download a CSV file Export Change Logs with a History of
with information about the history of op Administration Operations [page 173]
erations by tenant administrators.
User Management Administrators can manage the users in User Management [page 117]
the tenant.
Administrator Management Administrators can add new administra Manage Administrators [page 141]
tors and edit administrator authoriza
tions.
User Groups Administrators can create and delete User Groups [page 125]
user groups, and assign and unassign
users.
Corporate User Store SAP Cloud Platform Identity Configure Connection to a Corporate
Authentication service can be config User Store [page 84]
ured to use a corporate user store in ad
dition to its own user store.
Risk-Based Authentication Administrators define rules for authenti Configure Risk-Based Authentication
cation in accordance with the risk [page 51]
Self-services Users can use services to maintain or User Guide [page 182]
update their user profiles and to log on
to applications.
Service providers that delegate authentication to SAP Cloud Platform Identity Authentication service can use two
types of visualization of the web-based user interfaces for the logon pages of their applications - on a fullscreen of
the window and with overlay on top of the application page.
The use of overlays maintains the application context, by keeping the application page as dimmed background, to
provide for minimum disturbance to the work flow. The logon page is open in an iframe over the public page of the
application.
Fullscreen
When the overlay is not integrated in the application or the application does not provide a public one, or the user
opens directly a protected page of the application, then the user is redirected to the logon page and it is displayed
on fullscreen in the browser.
Related Information
The productive landscape represents the productive environment. It can be used by customer and partner
accounts only.
The productive landscape is available on a regional basis, where each region represents the location of a data
center:
A customer or partner account is associated with a particular data center and this is independent of your own
location. You could be located in the United States, for example, but operate your account in Europe (that is, use a
data center that is situated in Europe).
Table 11:
Data Center Landscape Host IP Address
Mozilla Firefox 10 (Firefox Extended Support Release - ESR) and latest ver
sion
Mozilla Firefox 10 (Firefox Extended Support Release - ESR) and latest ver
sion
Note
For security reasons, Safari on MAC OS 10.7 is not supported. Unlike Firefox or Chrome, Safari uses the
SSL libraries provided by the operating system. There are known security issues with this version of the
SSL libraries.
The end user screens, such as logon, forgot password, reset password, etc, of the applications that use SAP Cloud
Platform Identity Authentication service for authentication support the following browsers:
Table 14:
Web Browser Supported Version
Note
You cannot use versions 7 and 8 of Microsoft Internet Explorer for some user interfaces (responsive user
interfaces).
Table 15:
Web Browser Supported Version
The administration console for SAP Cloud Platform Identity Authentication service supports only English
language.
The end user screens, such as logon, forgot password, reset password, etc, of the applications that use SAP Cloud
Platform Identity Authentication service for authentication support the following languages:
Table 16:
Name of Language ID of Language (ISO 639-1 Format)
German de
English en
Spanish es
French fr
Japanese ja
Korean ko
Dutch nl
Polish pl
Portuguese pt
Russian ru
Chinese zh
Italian it
Welsh cy
Hebrew he
The language for the end user screens is set according to the following order of priorities:
1. If the locale is set, the end user screen uses the language set there.
Setting the locale, sets an Identity Authentication cookie. This cookie is used for all the applications in this
session that are configured to use Identity Authentication as identity provider.
Note
The locale can be set in either of the following ways:
Source Code
Source Code
https://<tenant ID>.accounts.ondemand.com/public/setLocale?locale=DE
2. If the locale is not set, the end user screen uses the language that the user's browser is set to.
○ If the language is not in the list of supported languages, the end user screen uses English instead.
○ If the language is in the list of supported languages, the end user screen uses this language.
SAP Cloud Platform Identity Authentication service is offered as part of some SAP Cloud Platform packages or as
a standalone product.
For more information how to get Identity Authentication, see SAP Cloud Platform Pricing and Packaging Options
, or contact your SAP sales representative.
After you have purchased a subscription for your Identity Authentication tenant, you receive an e-mail with a link
to the landing of the administration console for Identity Authentication and you can confirm the registration of
your first administrator user.
Note
If you experience troubles in accessing your Identity Authentication tenant, you can create an Incident on SAP
Support Portal with a component BC-IAM-IDS.
Related Information
SAP Cloud Platform Identity Authentication service supports scenarios for consumers (business-to-consumer
scenarios), for partners (business-to-business scenarios), and for employees (business-to-employee scenarios).
Related Information
The business-to-consumer scenario is related to any actions performed by the consumer, such as registration to
applications and consumer retailing. In this scenario, administrators facilitate the consumer processes, but they
do not act on the consumer's behalf.
Example
Michael Adams is an administrator at retail company A, and he would like to configure his system such that
users can register on their own and then purchase from the company’s site. Michael also wants to allow users
to access his Company A Purchasing application by self-registration. To do this , Michael logs on to the
administration console for SAP Cloud Platform Identity Authentication service, navigates to Applications
Company A Purchasing and chooses Authentication and Access User Application Access . He selects
the Public radio button to allow user self-registration for his Company A Purchasing application. Michael also
allows users to authenticate through a social provider by providing the keys and secrets for the social providers
after he chooses the Social Identity Providers tile. He then enables social sign-on by choosing the Applications
tile and navigating to Company A Purchasing Authentication and Access . Furthermore, Michael
configures custom terms of use and privacy policy for the Company A Purchasing application. To do this, he
chooses the Terms of Use Documents and Privacy Policy Documents tiles and adds the new plain text files in
Michael also decides to use a custom branding style for the buttons on his logon and registration forms. To do
this, he opens the Branding Style page under the Branding and Layout tab in the Application view and selects
the branding styles.
Donna Moore is a customer who wants to purchase goods from company A for the first time. When she
accesses company A’s application, she is redirected to the company’s logon page. Because she is not
registered yet, she has to choose the Register Now link to start the registration process. A registration form
then appears, prompting Donna to enter her names, e-mail, and address and to accept the organization's
terms of use and privacy policy. When she submits the form, she receives an e-mail with instructions on how to
activate her registration. Once she activates her registration, she is able to log on to the retailing application
with her user credentials.
Related Information
The business-to-business scenario is related to services for business partners. Unlike the business-to-consumer
scenario, consumer self-registration is not allowed, and the administrator of the company is usually the one that
triggers the user registration process.
The administrator invites partners or registers them on their behalf.
Example
Donna Moore is a tenant administrator at company A. This company is a goods and services retailer. She would
like to invite five transportation companies to join her organization in helping the distribution of goods and
services to distant locations. The distributors will purchase from the Company A Distribution application. For
this purpose, Donna registers these distributors on their behalf, logs on to the administration console for SAP
Cloud Platform Identity Authentication service, navigates to Applications Company A Distribution page,
and chooses Authentication and Access User Application Access . She selects the Private radio button in
order to restrict access to just these users. The partners then activate their registration via the on-behalf
registration e-mail and can log on to the Company A Distribution application.
The business-to-employee scenario is related to services for employees of an organization. Employees can access
various applications with one logon. Furthermore, administrators can upload employees data by using the user
import functionality.
Example
Julie Armstrong is an administrator at company B. She wants to configure a leave request application to be
used by the employees of the company. For this purpose, she imports the employees by opening the Import
Users page in the administration console for SAP Cloud Platform Identity Authentication service and selecting
a CSV file containing the employees. Once she has imported all the new users into the system, she sends them
an e-mail with instructions about how to activate their accounts via the Forgot Password process. She also
configures the trust on SAP Cloud Platform.
Because Julie wants only the employees to access the application, she selects the Internal radio button after
she chooses Authentication and Access User Application Access for the leave request application in the
administration console.
As an employee of company B, Michael accesses an SAP Cloud Platform application to make a leave request.
When he opens the application, he has to choose the Forgot Password link to activate his account. After
activation, Michael provides a user name and password to log on to the leave request application with. He is
redirected to Identity Authentication for authentication. Identity Authentication verifies his credentials and
sends a response back to the SAP Cloud Platform application. As a result, Michael logs on and enters his leave
request.
This guide is for administrators, and explains how administrators can configure SAP Cloud Platform Identity
Authentication service so that users can have all enhanced features for each scenario.For these configurations,
administrators mainly use the administration console for Identity Authentication, a Fiori-based user interface
adaptive to most browsers.
This section describes how you can configure the user authentication and access to an application, and how you
can set your application to use a custom privacy policy, terms of use, a branding style, and e-mail templates in
accordance with your company requirements. It also explains the trust configuration between SAP Cloud
Platform Identity Authentication service and a service provider.
Types of Applications
In SAP Cloud Platform Identity Authentication service you can create and configure your own custom applications
(SAML 2.0 service providers).
Apart from the custom applications that you can create, the tenant of SAP Cloud Platform Identity Authentication
service has two additional system applications, Administration Console and User Profile, previously
called SAP Cloud Identity, that are predefined with the creation of the tenant.
Note
In some tenants, the User Profile application still bears its previous name, SAP Cloud Identity.
Tip
If Administration Console or User Profile are not in the list of the system applications you may request
them. To do this, create a ticket on SAP Support Portal under the component BC-IAM-IDS.
For more information, how to create a custom application, see Create a New Application [page 29].
The Administration Console application contains the configurations of the administration console for SAP
Cloud Platform Identity Authentication service.
● to configure stronger protection for the administration console for SAP Cloud Platform Identity
Authentication service via the Risk-Based Authentication option.
● to configure stronger password requirements for the tenant administrators of the administration console for
SAP Cloud Platform Identity Authentication service.
● to customize the look and feel of the logon page of the administration console for SAP Cloud Platform Identity
Authentication service.
The User Profile application contains the configurations of the Profile Page.
● to define custom e-mail template sets for users created via the Add User option in the administration console
for SAP Cloud Platform Identity Authentication service, or via the SCIM REST API.
● to customize the look and feel of the logon page of the Profile Page.
Configuring Applications
Table 17: Configuring Applications
How to create an application and configure its display name ● Create a New Application [page 29]
● Change an Application's Display Name [page 30]
● Configure an Application's Home URL [page 31]
● Visit an Application's Web Page [page 32]
How to configure API Authentication ● Configure a Certificate for API Authentication [page 49]
● Configure Credentials for HTTP Basic Authentication
[page 48]
How to choose an identity provider for an application ● Choose Identity Provider for an Application [page 73]
You can create a new application and customize it to comply with your company requirements.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The display name of the application is displayed on the logon and registration pages.
Once the application has been created, the system displays the message Application <name of
application> created.
4. Configure the SAML 2.0 trust with the service provider.
5. If necessary, configure the application.
Related Information
Prerequisites
You are assigned the Manage Applications role. For more information about how to assign administrator roles, see
Edit Administrator Authorizations [page 146].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
4. Click the name of the application and change it in the pop-up dialog.
5. Save your changes.
Once the application has been updated, the system displays the message Application <name of
application> updated.
Related Information
You can configure the Home URL of an application in the administration console for SAP Cloud Platform Identity
Authentication service.
Context
Home URL is the URL that the user is redirected to after being authenticated. Initially, the Home URL for an
application is not configured in the administration console for Identity Authentication. Once the URL has been set,
you can change it.
Remember
Home URL is necessary when you import new users in Identity Authentication. Identity Authentication needs to
send activation e-mails to the new users and the home URL has to be mentioned in the e-mails. To access the
application, the users have to activate their accounts. For more information see Import or Update Users for a
Specific Application [page 68].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
○ If you are editing the URL, choose Edit from the list item, and type the new address in the pop-up dialog.
5. Save your changes.
Once the application has been updated, the system displays the message Application <name of
application> updated.
You can navigate to an application's Web site directly from the administration console for SAP Cloud Platform
Identity Authentication service.
Prerequisites
You have configured Home URL for the application in question. For more information, see Related Information.
Context
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Related Information
As a tenant administrator, you can delete one or more custom applications in a tenant of SAP Cloud Platform
Identity Authentication service.
Prerequisites
● You are assigned the Manage Applications role. For more information about how to assign administrator roles,
see Edit Administrator Authorizations [page 146].
Context
A Delete Applications operation removes the application and all of its configurations from the tenant of Identity
Authentication.
Note
You can only delete custom applications. The system applications in your tenant are hidden when you enter
Delete Applications mode in the administration console for Identity Authentication.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Once the application or applications have been deleted, the system displays the message <number>
applications deleted.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Tip
Type the name of the application in the search field to filter the list items.
4. Choose the Delete button in the right-hand panel to delete the selected application.
5. Confirm the operation in the pop-up dialog.
Once the application has been deleted, the system displays the message 1 application deleted.
This document is intended to help you configure a trusted service provider (SP) in the administration console for
SAP Cloud Platform Identity Authentication service by uploading its metadata or by entering the service provider
information manually. You can enter manually the name of the service provider, its endpoints, and its signing
certificate.
Prerequisites
You have the service provider metadata. See the service provider documentation for more information or contact
the administrator of the service provider.
To configure a trusted service provider in the administration console for SAP Cloud Platform Identity
Authentication service proceed as follows:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Note
Use a file with an extension .xml.
On service provider metadata upload, the fields are populated with the parsed data from the XML file. The
minimum configuration is to complete the Name field.
Field Description
Assertion Consumer Service Endpoint The SP's endpoint URL that receives the response with the
SAML assertion from Identity Authentication.
Single Logout Endpoint The SP's endpoint URL that receives the logout response
or request (for a scenario with multiple service providers)
from Identity Authentication for the termination of all
current sessions.
Restriction
The Metadata File, Name, Assertion Consumer Service Endpoint, and Single Logout Endpoint fields are not
editable for the system applications.
Once the application has been changed, the system displays the message Application <name of
application> updated.
Next Steps
Note
To see how to download the SAML 2.0 metadata describing Identity Authentication as identity provider
read Tenant SAML 2.0 Configuration [page 76].
Note
See the service provider documentation for more information about how to configure the trust.
Tip
If you use SAP Cloud Platform as a service provider, see Integration with SAP Cloud Platform [page 255].
Related Information
After configuring the user attributes to be collected by the registration and upgrade forms, you have to specify
how these attributes are sent to the application in the SAML 2.0 assertion.
Context
SAP Cloud Platform Identity Authentication service defines default names for these assertion attributes, but you
can change them in accordance with your requirements. You configure the attributes by defining which assertion
attribute corresponds to the user attribute that you set for the registration and upgrade forms. You can also
specify multiple assertion attributes for each user attribute. You perform this mapping to help the application use
the same user attribute for different scenarios that require several assertion attributes.
Table 18:
User Attribute Assertion Attribute Name
Salutation title
E-mail mail
Language language
User ID uid
Note
For example, consumer, partner, or employee.
City city
Country country
State/Province state
Department department
Division division
Company company
Groups groups
Note
This attribute is applicable for the corporate user store
scenarios and contains the groups the user in the corpo
rate user store is assigned to.
Note
The User Attribute column lists the attributes that can be shown on the registration and upgrade forms. The
Assertion Attribute Name lists the attributes that are sent in the assertion.
The configured custom attributes can be seen at the user profile page at https://<tenant
ID>.accounts.ondemand.com/ after choosing View My Data.
Remember
In scenarios when the application is using for authentication a corporate identity provider, and the Identity
Federation option is disabled, the user attributes configurations in the administration console for Identity
Authentication are not relevant. In such scenarios Identity Authentication sends to the application the user
attributes that come form the corporate identity provider without changing them. For more information about
the corporate identity provider scenario, see Corporate Identity Providers [page 148] and Configure Identity
Federation with the User Store of SAP Cloud Platform Identity Authentication Service [page 166].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
If the operation is successful, you receive the message Assertion attributes updated.
This is a profile attribute that SAP Cloud Platform Identity Authentication service sends to the application as a
name ID. The application then uses this attribute to identify the user.
Context
● By user ID
Note
This is the default setting.
● By e-mail
● By display name
● By logon name
● By employee number.
Note
User ID, E-Mail, Display Name, and Login Name are unique for the tenant.
The configuration of the name ID attribute for the system applications is disabled. The default setting for these
applications is User ID.
Caution
Identity Authentication does not check the Employee Number attribute for uniqueness. Be sure that the users
receive unique employee numbers.
Remember
In scenarios when the application is using for authentication a corporate identity provider, and the Identity
Federation option is disabled, the name ID attribute configurations in the administration console for Identity
Authentication are not relevant. In such scenarios Identity Authentication sends to the application the name ID
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been changed, the system displays the message Application <name of
application> updated.
Related Information
In addition to the user attributes, you can also configure attributes with default values for the application.
These attributes are sent from SAP Cloud Platform Identity Authentication service to the application in the SAML
2.0 assertion. You can set default attributes location and company with values Europe and Company A for
example, so that the application displays Europe and Company A on its main page.
Remember
In scenarios when the application is using for authentication a corporate identity provider, and the Identity
Federation option is disabled, the default attributes configurations in the administration console for Identity
Authentication are not relevant. For more information about the corporate identity provider scenario, see
Corporate Identity Providers [page 148] and Configure Identity Federation with the User Store of SAP Cloud
Platform Identity Authentication Service [page 166].
The configuration of the default attributes for the system applications is disabled.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
If the operation is successful, you receive the message Default attributes updated.
Related Information
Table 19:
How to define rules for authentication in accordance with the Configure Risk-Based Authentication [page 51]
risk
Enable social sign-on authentication for an application Enable or Disable Social Sign-On for an Application [page
44]
How to allow users to log on to an application from the corpo Enable or Disable Kerberos Authentication for an Application
rate network without entering their username and password [page 47]
How to configure the type of authentication when API meth API Authentication [page 48]
ods of SAP Cloud Platform Identity Authentication service are
used
Social sign-on allows users to link their SAP Cloud Platform Identity Authentication service accounts with social
network accounts. To link the accounts, users have to choose the social provider button on the logon page of a
cloud application. When authenticated via their social identity provider, users are prompted to allow their
accounts to be linked with the social network accounts. After this initial setup, users can log on to the application
without additional authentication.
You have set the keys and secrets for the social providers. For more information, see Configure Social Identity
Providers [page 169].
Context
Identity Authentication allows account linking with the following social providers:
● Twitter
● Facebook
● LinkedIn
● Google
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
With Social Sign-On users can log on to the application via one of the social providers. They can see this option on
the logon page.
Which social identity providers logos appear on the logon page of the application depend on the configurations
you have made. For more information, see Configure Social Identity Providers [page 169].
Related Information
You enable Kerberos authentication to allow users to log on to an application from the corporate network without
entering their username and password.
Prerequisites
You have configured Kerberos authentication for the tenant. For more information, see Configure Kerberos
Authentication [page 95].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
Developers can choose the type of authentication when API methods of SAP Cloud Platform Identity
Authentication service are used.
For more information about the API methods, see Invitation REST API [page 198] and User Management REST
API [page 200].
The certificate to be used for authentication by the REST APIs of Identity Authentication must be requested from
the SAP Support Portal .
This document describes how developers set basic authentication when API methods of SAP Cloud Platform
Identity Authentication service are used.
Context
You can use a user ID and a password to authenticate when REST API calls to the tenant of Identity Authentication
are used. The system automatically generates a user ID when the password is set for the first time.
Note
The password must meet the following conditions:
The password is locked for 60 min after 5 failed logon attempts with wrong value.
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Note
If you are setting the password for API authentication for the first time, these fields are empty.
Once the password has been saved, the system displays a message informing you of this.
This document describes how developers configure the certificate used for authentication when API methods of
SAP Cloud Platform Identity Authentication service are used.
Prerequisites
You have requested a client certificate from the SAP Support Portal .
For the configuration, you have to provide the base64-encoded certificate as a file or plain text.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Note
For the upload, you have to use .cer or .crt files.
Once the certificate has been uploaded, the system displays the message Certificate for API
authentication updated.
Related Information
You can define rules for authentication according to different risk factors. The configured rules manage
authentication according to IP range (specified in CIDR notation) and group membership of the authenticating
user.
Authentication Rules
The added rules are displayed sorted by priority. When a user tries to access the application, the rules evaluate if
the user meets the criteria of the rule, starting with the rule with the highest priority, until the criteria of a rule are
met. If the criteria of a rule are met, the rest of the rules are not evaluated.
If none of the authentication rules meets the criteria, the default authentication rule is applied. For the default
authentication rule, you can only configure Action. The rule is valid for any IP range or Group.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
If you do not have a created application in your list, you can create one. For more details, see Related
Information.
Caution
The list also includes the Administration Console application. If you enable risk-based authentication
for that application, make sure that you, as a tenant administrator, meet the authentication rules and the
default authentication rule. Otherwise when you log out of the administration console of Identity
Authentication you will not be able to log in it again if you don't meet the rules.
If Administration Console is not in the list of the applications you may request it. To do this, you need
to create a ticket with a subject on SAP Support Portal under the component BC-IAM-IDS.
Option Description
Edit an existing rule Choose the icon next to the rule you want to edit.
Delete an existing rule Choose the delete icon next to the rule you want to delete.
Note
By default any user can log on from any IP.
Once the application has been updated, the system displays the message Authentication rules
updated.
Examples
Donna Moore, as an administrator of company A, would like to configure Identity Authentication to always ask the
company employees for a password and a passcode (two-factor authentication) to log on to a Leave Request
application. For this purpose, Donna sets only a Default Action:
Michael Adams, as an employee of company A, wants to create a leave request and is prompted to provide two
factors (a password and a passcode generated by an authenticator app on his mobile device) to log on to the
Leave Request application, regardless of whether he is in the corporate network or on a business trip. Michael's
manager, Julie Armstrong, receives a notification that Michael has created a leave request, and approves this by
logging on to the application with two factors (a password and a passcode generated by her mobile device).
Example 2
Donna Moore, as an administrator of company A, would like to configure Identity Authentication to allow the
company employees to log on to a Leave Request application from the corporate network with a user name and a
Authentication Rules
Table 20:
Michael Adams, as an employee of company A, accesses the application in his office and logs on with his
username and password. When he is on a business trip, he can create leave requests by providing two factors (a
password and a passcode generated by an authenticator app on his iPhone). Michael's manager, Julie Armstrong,
receives a notification that Michael has created a leave request and approves this by logging on to the application
with two factors (a password and a passcode generated by her Android phone).
Related Information
Context
● Action
This action will be performed if the IP range or the Groups membership of the authenticating user meet the
defined criteria.
You can choose one of the following actions:
○ Allow
Note
Passcodes are time-based and valid for one logon attempt only.
Note
By default the field is empty, meaning that any IP is allowed.
Example
Enter 123.45.67.1/24 to allow users to log on from any IP starting with 123.45.67.
The fields IP Range and Group are not mandatory, but one of both has to be specified.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
If you do not have a created application in your list, you can create one. For more details, see Related
Information.
Caution
The list also includes the Administration Console application. If you enable risk-based authentication
for that application, make sure that you, as a tenant administrator, meet the authentication rules and the
default authentication rule. Otherwise when you log out of the administration console of SAP Cloud
Platform Identity Authentication service you will not be able to log in it again if you don't meet the rules.
If Administration Console is not in the list of the applications you may request it. To do this, you need
to create a ticket with a subject on SAP Support Portal under the component BC-IAM-IDS.
Related Information
You can configure a custom logo for a specific application by uploading an image. Furthermore, you can remove a
configured logo and leave the display name only as a title for the application.
The logo is displayed on the application's logon page and can be included into the e-mails sent to users.
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
You can use one of the following formats for the image: <name>.png, <name>.gif, and <name>.jpeg.
Note
The image must be smaller than 100 KB and with a maximum size of 300x100.
Related Information
This section shows you how to display or hide the name of the application from the logon page.
Prerequisites
You are assigned the Manage Applications role. For more information about how to assign administrator roles, see
Edit Administrator Authorizations [page 146].
Context
The application's display name is the name that appears on the left side of the logon and registration pages of the
applications that use SAP Cloud Platform Identity Authentication service for authentication. You set this name
when you first create your application in the administration console for Identity Authentication, and you can
change it later. For more information, see Create a New Application [page 29] and Change an Application's
Display Name [page 30].
By default, the display name of the application is set to appear on the logon page.
Caution
Be careful when you switch off the display of the application name. The users might not be sure which
application they are providing their credentials for.
To configure the appearance of the application's name on the logon page, proceed as follows:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
Results
Depending on your choice, the display name of the application is visible or hidden on the logon page.
For the configuration of the branding style, you can choose a style for the logon, registration, and upgrade forms,
or you can customize the buttons on these forms.
Context
● Default Theme
This predefined theme includes white and brand blue coloring based on SAP Fiori’s color palette.
Note
This is the default setting.
● Custom Theme
The custom theme allows you to configure a custom branding style for the buttons, and uses the Default
theme for all other elements on the forms. For this configuration, you can customize the top and bottom
background color of the button, the button's border line color, and the color of the button's text.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
If your option is Custom Theme, configure the button colors. To configure the button colors, you can use the
color picker or enter the color's hexadecimal value.
7. Save your selection
Once the application has been changed, the system displays the message Theme changed to <name of
theme>.
Related Information
You can enable or disable the reload of the application's parent page after a successful logon.
Context
The Reload Parent Page option specifies whether the application's parent page reloads or not after a successful
logon via an overlay page.
Note
By default the Reload Parent Page option is enabled. Disable the option if you would like to embed the login
page in your custom iFrame.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
Context
The template set contains templates for different application processes such as self-registration, on-behalf
registration, invitation, and password upgrade. Initially, the application uses a default template set with an English
language version for all the templates in the set. This template set is named Default. If you want to use another e-
mail template set, you have to set it to the respective application.
To use a custom template set, you can request it from an operator of SAP Cloud Platform Identity Authentication
service. You need to create an incident on SAP Support Portal with a component BC-IAM-IDS. You should
provide information of the content of the e-mail template for the respective application process. For that purpose,
you need to open the template set for the respective application process from the links in the table bellow, edit the
texts according to your needs, and attach your versions of the documents in the incident.
If you want to use a custom template set in another language, you need to open the template set for the
respective application process from the links in the table bellow, edit the texts in the respective language, and
attach your versions of the documents in the ticket.
Caution
You should use the same placeholders as those used in the template documents.
When you edit texts in languages written in Right-To-Left (RTL) direction check that the placeholders are
situated in the right place.
● English
● German
● Spanish
On-Behalf Registration This e-mail template is used after some ● HTML document
body else registers on-behalf of a user. It ● TXT document
should contain registration information.
Forgot Password This e-mail template is used when a user ● HTML document
creates a new password. It should con ● TXT document
tain password update information.
Reset Password This e-mail template is used when a us ● HTML document
er's password has expired. It should con ● TXT document
tain password reset instructions.
Note
Both the HTML and TXT formats are included in the e-mails sent to a user. What the user sees, depends on the
settings of his or her e-mail client.
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
Related Information
In the administration console, you can configure which user attributes SAP Cloud Platform Identity Authentication
service sends to the service provider to be displayed on application's registration and upgrade forms.
After the user has filled in the form, the information from these attributes is recorded in the user's profile. This is
why these attributes are also called profile attributes and are handled by the profile services.
Context
To configure the profile attributes, you need to specify which personal, company, and contact information the
application prompts the user to provide when registering or upgrading. The information that the user has to
provide depends on the status of the attribute (required or optional). You configure which attributes are displayed
as required or optional in the administration console for Identity Authentication.
PERSONAL INFORMATION
● Salutation
● First Name
● Middle Name
● Last Name
● E-mail
● Password
Note
The Last Name, E-mail, and Password attributes are always required for user registration or upgrade, so
they are not configurable.
● Phone
● Street Address
● Street Address 2
● City
● Zip/Postal Code
● Country
Note
The Country parameter is required when the Zip/Postal Code is filled in by the user in the registration
form. For example, this is the situation when both Zip/Postal Code and Country are optional, and the
user fills in the Zip/Postal Code field. If the user deletes the information in the Zip/Postal Code the
Country parameter becomes optional.
● State/Province
Note
The State/Province attribute is configurable only if the Country attribute is enabled.
● Company
● Street Address
● Street Address 2
● City
● ZIP/Postal Code
● Country
Note
The Country parameter is required when the Zip/Postal Code is filled in by the user in the registration
form. For example, this is the situation when both Zip/Postal Code and Country are optional, and the
user fills in the Zip/Postal Code field. If the user deletes the information in the Zip/Postal Code the
Country parameter becomes optional.
● State/Province
Note
The State/Province attribute is configurable only if the Country attribute is enabled.
● Industry
● Relationship
● Job Function
CONTACT PREFERENCES
● By E-mail
● By Telephone
Note
The CONTACT PREFERENCES attributes define if the self-registration form contains a section "Contact
Preferences" that asks the user if he or she would like to be contacted by e-mail or phone, or both. The
presence of this section depends also on the Country attribute, since the legislation in some countries require
the user to explicitly agree that he or she would like to be contacted by e-mail or phone, or both.
● If one or both CONTACT PREFERENCES parameters are enabled, and both Country parameters are
disabled the "Contact Preferences" section will appear in the registration form.
● If one or both Country parameters and one or both CONTACT PREFERENCES parameters are enabled, the
"Contact Preferences" section will appear in the registration form if the user types at least one country
which requires the user to explicitly agree that he or she would like to be contacted by e-mail or phone, or
both.
● If both CONTACT PREFERENCES parameters are disabled, the "Contact Preferences" section will not
appear in the registration form.
For the full set of the countries that do not require the user to explicitly agree that he or she would like to be
contacted by e-mail or phone copy the respective URL listed below, replace <tenant ID> with your Tenant ID,
and open the edited URL in a Web browser.
By E-Mail https://<tenant
ID>.accounts.ondemand.com/md/
implicitOptInEmailCountryKeys
By Telephone https://<tenant
ID>.accounts.ondemand.com/md/
implicitOptInTelefonCountryKeys
In addition to these profile attributes, the registration and upgrade forms include terms of use and privacy policy
documents that are configured separately.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
If the operation is successful, you receive the message Registration form updated.
Context
You can configure the application to restrict access to specific users only. The following access configurations are
possible:
● Public
All users are allowed to log on. Unregistered users start the self-registration process by choosing the Register
Now link on the logon page.
Note
You have to add as trusted the domains for those applications that allow self-registration to the users. For
more information, see Configure Trusted Domains [page 80].
Tip
For more information how to add new users in the user store of Identity Authentication, see Create a New
User [page 119].
You can also import new users in Identity Authentication via a CSV file. For more information, see Import or
Update Users for a Specific Application [page 68].
● Private
Only users registered by an application can log on. To register users for a specific application, you have to
import these users via a CSV file. For more information, about the user import, see Import or Update Users for
a Specific Application [page 68].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
If the application is updated, the system displays the message Application <name of application>
updated.
Related Information
As a tenant administrator, you can import new users or update existing ones for a specific application with a CSV
file, and send activation e-mails to the users that have not received activation e-mails for that application so far.
Prerequisites
● You are assigned the Manage Users role. For more information about how to assign administrator roles, see
Edit Administrator Authorizations [page 146].
Note
You need the metadata to configure the trust between the service provider and SAP Cloud Platform
Identity Authentication service, which is in the role of identity provider.
Context
By importing new users with a CSV file, you create user profiles without passwords in Identity Authentication. As a
result, the users receive e-mails with instructions how to activate their accounts. After the users set their
passwords, they can log on to the application for which they were imported. Based on the user access
configuration of the application, the users can log on to other applications connected with the tenant in Identity
Authentication.
In addition to the new user import, you can specify existing users in the imported CSV file. You thus define the
users to be updated in Identity Authentication.
By specifying existing users in the imported CSV file you can also restrict the access to a specific application via
the Private options. For more information, see Configure User Access to the Application [page 67].
The CSV file contains columns such as status, loginName, mail, firstName, lastName, language validTo, validFrom,
spCustomAttribute1, spCustomAttribute2, spCustomAttribute3, spCustomAttribute4, spCustomAttribute5, and
groups.
The status, mail and lastName columns are mandatory, and they must always have values.
The status, loginName, mail and firstName columns must be with a string value of up to 32 characters. The
lastName column must be with a string value of up to 64 characters.
The language column must be with a string value specified by a two-letter code defined in ISO 639-1. If you have
defined an e-mail template set for the language that is set in the language column, the user will receive the
activation e-mail in that language.
The validFrom and validTo columns must be with a string value in the Zulu format yyyyMMddHHmmss'Z'.
Note
The information in the validFrom and validTo columns can be processed by the service provider in order to limit
user access, but it would not affect the authentication of the user.
The status column defines whether the user is still active in the system and is able to work with any tenant
applications. When a user is deleted, it is rendered inactive.
The groups in the groups column must be existing. You cannot add a user to a user group that is not existing. For
more details how to list or create user groups, see Related Information.
Caution
You cannot change the e-mail of an existing user.
Example
A tenant administrator decides to import three new users (Michael, Julie, Donna) and to update two others
(John and Denise) that will use the company's applications. Michael is a member of three groups, namely
Employees, Managers and HR. John and Denise were inactive users that now use tenant's applications. The
administrator would also like to update another user (Richard) who currently does not work for the company.
To do this, the administrator uploads a CSV file with the following information:
Table 23:
status logi mail first last lan validFrom validTo spCustomAttri groups
nName Name Name guage bute1
Note
When there are more than one user groups that have to be added for a single user, the groups are received
in the SAML 2.0 assertion under the following format:
<Attribute Name="groups">
<AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"
xsi:type="xs:string"
>Managers</AttributeValue>
<AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"
xsi:type="xs:string"
>Employees</AttributeValue>
<AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"
xsi:type="xs:string"
>HR</AttributeValue>
</Attribute>
The users that have not received activation e-mails will receive such e-mails, and then can activate their
accounts and log on.
To import users for an application into Identity Authentication, and to send activation e-mails, proceed as follows:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
4. Choose the Browse... button and specify the location of the CSV file.
If the operation is successful, the system displays the message Users imported or updated.
6. Choose the one of the following options:
Option Description
Do nothing The users are imported or updated for the selected application, but they will not receive activation e-
mails. The activation e-mails will be sent when you choose Send E-Mails Send .
Repeat steps 1 The users are imported or updated for the selected application, but they will not receive activation e-
to 5 mails. The activation e-mails will be sent when you choose Send E-Mails Send .
Choose This will send activation e-mails to all users that are imported for the selected application, but have not
Send E- received activation e-mails so far.
Mails
Note
Send
The Send button is inactive if Home URL or SAML 2.0 configuration of the application is missing. You
can only import users, but you cannot send activation emails.
You need the Home URL configured for the specific application to be able to send the activation e-
mails to the imported new users. For more information, see Configure an Application's Home URL
[page 31].
To access the application, the users have to activate their accounts by following the link they receive
in the e-mails.
Related Information
This section shows you how to choose an identity provider for an application.
Prerequisites
Context
You have the following options for an identity provider in the administration console for SAP Cloud Platform
Identity Authentication service:
Note
If you select this option, you will not be able to access the custom configurations for the applications. The
Authentication and Access and Branding and Layout tabs will not be visible.
Restriction
The option to choose an identity provider for the system applications is disabled. The default setting for these
applications is Identity Authentication, set as the default identity provider.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
Related Information
The mobile single sign-on (SSO) feature allows users to access applications protected with two-factor
authentication without the need to manually enter the one-time password (OTP), also called a passcode, via SAP
Authenticator.
Mobile single sign-on is applicable only when the applications are accessed via identity provider (IdP)-initiated
single sign-on (SSO). For more details about IdP-initiated SSO, see Related Information.
You also have to comply with the URL requirements for these applications. Users can add applications in SAP
Authenticator by scanning a QR code, which can be sent to them by the administrator, or by typing the
application's URL. The URL must have the following format:
https://<tenant_ID>.accounts.ondemand.com/saml2/idp/sso?
sp=<sp_name>[&RelayState=<sp_specific_value>&index=<index_number>]&j_username=[usernam
e]&j_otpcode=[passcode]
Related Information
Initially, the tenants are configured to use default settings. This section describes how you as a tenant
administrator can update the tenant display name, configure a global logo for the tenant, and view and download
SAML 2.0 configuration.
How to configure a custom global logo on the forms for logon, Configure a Tenant Logo [page 77]
registration, upgrade, password update, and account activa
tion for all applications in a tenant
How to configure the tenant's name Change a Tenant's Display Name [page 81]
How to view and download tenant SAML 2.0 metadata Tenant SAML 2.0 Configuration [page 76]
How to upload a new signing certificate Tenant SAML 2.0 Configuration [page 76]
How to configure the validity of the link sent to a user in the Configure E-Mail Link Validity [page 78]
different application processes.
The corporate user store scenario and how to configure SAP Corporate User Store [page 82] and Configure Connection
Cloud Platform Identity Authentication service to connect with to a Corporate User Store [page 84]
your corporate user store
How to disable or enable IdP-Initiated process via the adminis Configure IdP-Initiated SSO [page 99]
tration console for SAP Cloud Platform Identity
Authentication service.
How to protect an application when using responsive UIs, or Configure Trusted Domains [page 80]
embedded frames
You as a tenant administrator can view and download the tenant SAML 2.0 metadata. You can also change the
name format and the certificate used by the identity provider to digitally sign the messages for the applications via
the administration console for SAP Cloud Platform Identity Authentication service.
Context
To view and download the tenant SAML 2.0 metadata, or to change the name format, or the default certificate
used by the identity provider to digitally sign the messages, proceed as follows:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
○ To download the identity provider's metadata, press the Download Metadata File button.
○ To change the default signing certificate, upload the new certificate as a file, or insert it as a text, and save
your changes.
Note
By default Identity Authentication uses self signed certificates. The signing certificate can be a server's
self-signed certificate, a public root certificate, or a certificate belonging to a commercial Certificate
Authority (CA).
The new certificate must be a valid Base64-encoded X.509 certificate (.cer or .crt), and its public key
must be the same as the public key of the default certificate. The certificate should not include the
BEGIN and END tags.
If the change of the certificate is successful, the system displays the message Tenant <name of
tenant> updated.
Table 25:
Note
Tenant ID is an automatically generated ID by the system. The first administrator created for the
tenant receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Caution
You should change the name of the identity provider on the service provider side every time you
change the name format of the identity provider in the administration console for Identity
Authentication. If you have set trusts with more than one service provider, change the name in every
service provider. For more information about how to edit the name, see the documentation of the
respective service providers.
If the change of the name is successful, the system displays the message Tenant <name of tenant>
updated.
Related Information
You can configure a custom global logo on the forms for logon, registration, upgrade, password update, and
account activation for all applications in a tenant.
This means that this logo is displayed in the footer or in the header of the form that your users access to log on or
to register to an application. If you do not specify a company-specific tenant logo, the forms will display the
default SAP logo. SAP has configured the following default tenant logo.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The image file must have one of the following extensions: .png, .gif, or .jpeg.
Note
If the height of the image is larger than 36 pixels, the user forms will show the logo proportionally resized to
a height of 36 pixels as the quality will be preserved.
If the height of the image is lower than 36 pixels, the user forms will resize the image as the quality will be
deteriorated.
If the operation is successful, you will receive the following message: Tenant logo updated.
6. To restore the default logo, choose Restore Default.
If this operation is successful, you will receive the following message: Default logo restored.
Context
The tenant administrator can specify how long the link sent to a user in the various application processes (self-
registration, on-behalf registration, invitation, forgot password, locked password, reset password) will be valid for.
Self-Registration 21 Days
Invitation 28 Days
To change the validity period of the links, follow the procedure below:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
You can choose a value between 1 and 23 for Hours, and 1 and 30 for Days.
If the operation is successful, the system displays the message E-mail link validity updated.
This document describes how service providers that delegate authentication to SAP Cloud Platform Identity
Authentication service can protect their applications when using embedded frames, also called overlays, or when
allowing user self-registration.
Context
If you want to use overlays in your applications, you have to add the domains of these applications as trusted in
the administration console for SAP Cloud Platform Identity Authentication service. Otherwise the user will receive
an error message when trying to access the overlays of these applications.
You also have to add as trusted the domains for those applications that allow self-registration to the users. For
more information about the various access configurations in the administration console for Identity
Authentication, see Configure User Access to the Application [page 67].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
You can type either the full name of the host or you can use the wild card * function. See the examples:
mycompany.ondemand.com
*.example.com
6. Save your changes.
If the operation is successful the system displays the message Trusted Domains updated.
You can configure the tenant's name from the administration console for SAP Cloud Platform Identity
Authentication service.
Context
If you have not specified a specific tenant name, you will see the tenant ID instead.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Related Information
Overview
Identity Authentication can connect with the following corporate user stores:
This scenario works with an SAP Cloud Platform application named proxy and provided by an SAP Cloud Platform
account named sci. The proxy application on SAP Cloud Platform uses the OAuth authentication mechanism
when communicating with Identity Authentication. The connection between SAP Cloud Platform and the
corporate user store is carried out with an SAP Cloud Platform Connector.
Authentication Flow
When the Corporate User Store option is configured properly, and a user tries to access a trusted application for
the first time with the on-premise credentials, Login Name and Password entered correctly, the user is
For the first login with on-premise credentials, the user enters his or her Login Name and a Password. For
subsequent logins the user can use either his or her Login Name, E-Mail, or User ID, and the Password .
Note
The user in the corporate user store must have the mail attribute.
The tenant administrator needs to monitor and prevent the co-existence of a cloud and on-premise user with
one and the same e-mail address. The tenant administrator has to instruct the users to login for the first time
with their Login Name, not with the E-Mail.
If a user who has a user record in the cloud user store is deleted in the corporate user store, she or he will not be
able to authenticate using Identity Authentication. The user record for this user remains in the cloud user store,
and the tenant administrator can delete it via the administration console for Identity Authentication. For more
information, see Delete Users [page 123].
For all these users from the corporate user store, a second factor for authentication can be enabled for some
applications, or cloud user groups can be assigned. For more details, see Configure Risk-Based Authentication
[page 51] and Assign Groups to a User [page 129].
In the scope of the Corporate User Store scenario, you can manage access to applications and their resources on
the basis of the groups that are available in the corporate user store.
The corporate user groups are sent to an application in the SAML 2.0 assertion. corporate_groups is the
attribute that contains the groups that the user in the corporate user store is assigned to. For more details about
how the groups are sent to the application in the SAML 2.0 assertion, see Configure the User Attributes Sent to
the Application [page 38].
Note
If your application is deployed on the SAP Cloud Platform, the corporate user store groups, relevant for the
application, and contained in the corporate_groups attribute in the SAML 2.0 assertion, can be mapped to a
assertion-based groups created in SAP Cloud Platform cockpit. For more information, see the 4. (If Using an
Identity Provider) Define the Group-to-Role Mapping section in Managing Roles.
You can also restrict access to applications on the basis of membership in a corporate user group by setting
different rules via risk-based authentication. For more information, see Configure Risk-Based Authentication
[page 51].
When a user has been successfully authenticated for the first time with the credentials from the corporate user
store, a record for that user is created in SAP Cloud Platform Identity Authentication service with details taken
from the corporate user store. In this record, the user is created with a User Type employee. This User Type
cannot be changed.
For more information about the attributes taken from the Active Directory and their mapping to the user store of
Identity Authentication, see Configure SAP Cloud Platform When Connecting to an LDAP User Store in
Configure SAP Cloud Platform [page 84].
Related Information
To configure connection to a corporate user store, you have to make the following configurations in SAP Cloud
Platform and in SAP Cloud Platform Identity Authentication service.
Context
The configuration of SAP Cloud Platform depends on the type of the user store. You have two options for this:
LDAP user store and SAP NW AS Java user store.
Procedure
1. In the SAP Cloud Platform cockpit, choose Services in the navigation area Identity Authentication Add-On
Enable in the detailed view of the service .
This will enable the extension service of SAP Cloud Platform Identity Authentication service named proxy and
provided by an SAP Cloud Platform account named sci.
Caution
If you don't see the Identity Authentication Add-On tile in the cockpit, you need to create a ticket with a
subject "Enable Corporate User Store Feature" on SAP Support Portal under the component BC-IAM-
IDS. You have to provide information about your SAP Cloud Platform account name and data center.
2. In your consumer account on SAP Cloud Platform, register an OAuth client for the subscribed proxy
application provided by the sci account.
The procedure is described in the documentation of SAP Cloud Platform in the link below.
Note
Since Identity Authentication will create the subscription to the proxy application, the Prerequisites section
in the respective document is not relevant for the current scenario.
For the Authorization Grant field in the SAP Cloud Platform cockpit, choose Client Credentials from the
dropdown list.
For more information about how to register an OAuth client, see Registering an OAuth Client.
3. Install an SAP Cloud Platform Connector in your corporate network.
Note
You have to specify the SAP Cloud Platform settings. The Prerequisites section in the document describing
the configuration is already configured for the proxy application, and you should proceed with the
configuration steps. For more information, see Configuring User Store in the Cloud Connector.
For the User Path and Group Path fields, specify the LDAP tree that contain the users and groups,
respectively. For example, if the tree has the following structure:
Table 27:
User Path ou=People,dc=example,dc=com
Note
If you want to change the user attributes taken from Microsoft Active Directory, you can do it as part of the
configuration of the SAP Cloud Platform Connector via changing the default user attribute mapping. You
can also add the employeeNumber, division, department and organization attributes that are
defined in the SCIM Enterprise User Schema Extension.
SAP Cloud Platform Connector uses the SCIM protocol to transfer the data, so the Active Directory
attributes are mapped first to the SCIM attributes. When the data is provisioned, the SCIM attributes are
mapped to the user store attributes of Identity Authentication.
To change the default user attributes, or to add new user attributes you have to edit the whole file.
Caution
This file overwrites the configurations you made in Configuring User Store in the Cloud Connector.
In this section provide the same information as when you specified the SAP Cloud Platform settings in the
previous step.
{
"LDAPServers": [
{
"Host": "<The host name of the LDAP server to be contacted>",
We recommend that you configure this section, if you want to use SSL.
"MaxQueryTime": "60000",
"MaxQueryResults": "1000",
"MaxConnectionPoolSize": "10",
"PoolConnectionTimeout": "300000",
"CacheSize": "1000",
"CacheEntryValidity": "300000",
"MaxNumberOfFailedLogonAttempts": 5,
"UserLockTimeout": 1800000,
"UserObjectClass" : "user",
"GroupObjectClass" : "group",
"GroupAttributeDisplayName" : "cn",
"UserGroupRelation": {
"SourceClass": "user",
"SourceAttribute": "memberOf"
},
In this section define the mapping between the Active Directory user attributes and the SCIM user
attributes that will be sent via the Cloud Connector to the user store of Identity Authentication, or add the
{
"SingularAttributes": [
{
"SCIMAttribute": "userName",
"mappings": [
{
"LDAPAttribute": {
"name": "sAMAccountname"
}
}
]
},
"SCIMAttribute": "name",
"mappings": [
{
"SCIMSubAttribute": "givenName",
"LDAPAttribute": {
"name": "givenName"
}
},
{
"SCIMSubAttribute": "familyName",
"LDAPAttribute": {
"name": "sn"
}
},
{
"SCIMSubAttribute": "honorificPrefix",
"LDAPAttribute": {
"name": "personalTitle"
}
}
]
},
{
"SCIMAttribute": "displayName",
"mappings": [
{
"LDAPAttribute": {
"name": "displayName"
}
}
]
},
{
"SCIMAttribute": "locale",
"mappings": [
{
"LDAPAttribute": {
"name": "locale"
}
}
]
},
{
"SCIMAttribute": "timeZone",
"mappings": [
{
"LDAPAttribute": {
"name": "timezone"
}
}
The following table shows the default mapping between the Active Directory user attributes and the SCIM
attributes, and the existing maping between the SCIM attributes and the attributes in the user store of
Identity Authentication.
Table 28: Detailed Attribute Mapping Between Active Directory and SCIM, and between SCIM and the User Store of
SAP Cloud Platform Identity Authentication Service
Microsoft Active Directory Attrib SCIM Attributes SAP Cloud Platform Identity
utes Authentication Service User Store
Attribute
sn familyName lastName
l Addresses.locality city
st Addresses.region state
co Addresses.country country
Note
The attributes employeeNumber, division, department, costCenter in the Microsoft Active
Directory Attributes column are given as examples. They can differ according to the specific LDAP
properties containing these attributes.
Next Steps
Procedure
1. In the SAP Cloud Platform cockpit, choose Services tab Identity Authentication Add-On Enable in the
detailed view of the service. .
Note
You can log on to the cockpit at the URLs given below. Use the relevant URL for your associated region:
○ Europe: https://account.eu1.hana.ondemand.com/cockpit
○ United States: https://account.us1.hana.ondemand.com/cockpit
○ Asia-Pacific: https://account.ap1.hana.ondemand.com/cockpit
This will enable the extension service of Identity Authentication named proxy and provided by an SAP Cloud
Platform account named sci.
2. In your consumer account on SAP Cloud Platform, register an OAuth client for the subscribed proxy
application provided by the sci account.
The procedure is described in the documentation of SAP Cloud Platform in the link below.
For the Authorization Grant field in the SAP Cloud Platform cockpit choose Client Credentials from the drop
down list.
For more information about how to register an OAuth client, see Registering an OAuth Client.
3. Install an SAP Cloud Platform Connector in your corporate network.
Note
For this scenario, you have to do the following:
○ In the configuration of SAP Cloud Platform Connector, configure the host mapping to the on-premise
system. For more information, see Configuring Access Control (HTTP).
For the Limiting the Accessible Services for HTTP(S) section, be sure that the URL Path is /scim/v1,
and Path and all Subpaths radio button is chosen for Access Policy.
○ In the configuration of SAP Cloud Platform cockpit, create a destination to the on-premise system.
Note
The relevant prerequisites for this scenario are:
○ You have a SAP NetWeaver 7.2 or higher Application Server for the Java system.
○ You have installed and deployed federation software component archive (SCA) from SAP Single
Sign-On (SSO) 2.0. For more information, see Downloading and Installing the Federation
Software.
Since Identity Authentication has already deployed the proxy application, you should start from the
2. Configure the On-Premise System section in the documentation.
For more information, see Using an SAP System as an On-Premise User Store
When configuring the destination to the on-premise system, make sure of the following:
○ The Type is None.
○ The protocol of the URL is HTTP.
○ The URL of the destination, the host name and the port should coincide with the virtual host
name and virtual port from the setup of the access control in SAP Cloud Platform Connector.
○ The Proxy Type is OnPremise.
○ The Authentication is BasicAuthentication.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
You will not see this list item if the feature has not been enabled by an Identity Authentication operator.
4. Select your SAP Cloud Platform account's data center, enter your SAP Cloud Platform consumer account,
and the OAuth client ID and secret.
Note
The Client ID and Client Secret fields in the administration console for Identity Authentication have to
match the ID and Secret registered on SAP Cloud Platform under the OAuth Settings tab for your consumer
account.
The Account Name field in the administration console for Identity Authentication has to match your SAP
Cloud Platform Account Name.
If the operation is successful, you receive the message Connection settings saved.
Results
When the configuration is complete, the user can log in to the application with the on-premise credentials. The
first login requires Login Name and password. After successful authentication, a new user record is created in
Identity Authentication with type employee.
Overview
You configure Kerberos authentication for SAP Cloud Platform Identity Authentication service in order to allow
users to log on without a username and password when they are in the corporate network. Identity Authentication
supports Kerberos with Simple and Protected GSS-API Negotiation Mechanism (SPNEGO).
● Web client
The Web client requests a protected resource of an application configured to use Identity Authentication as
an identity provider and authenticates against the Key Distribution Center (KDC). For example, users can use
the Web browser to access cloud applications using Identity Authentication.
● Key Distribution Center (KDC)
It authenticates the user and grants a ticket that is used for the communication between the Web client and
Identity Authentication.
● Identity Authentication
Identity Authentication accepts the ticket issued by the KDC and checks the authenticating user in its cloud
user store.
Related Information
1.5.2.7.1 Prerequisites
● You have configured the Web browser (Web client) to use Kerberos authentication.
For more information about this procedure, see the corresponding browser (client) documentation.
Tip
This setting is usually found under the Local Intranet tab or the Trusted Sites list in the browser. Search on
the Internet or in your browser documentation for information about how Kerberos authentication is
enabled.
● You have a tenant for SAP Cloud Platform Identity Authentication service.
● The trust with the service provider of Identity Authentication is configured.
For more information, see Integration Scenarios [page 255].
● The users logging on with Kerberos authentication exist in the cloud user store with the required details.
Each user has to have a login name as a user attribute. This is specified under the loginName column in the
imported CSV file. For details, see Related Information.
Related Information
Context
This procedure is performed by the domain administrator. If you are not a domain administrator, skip to the next
section.
Procedure
1. Create a service user in KDC (in Microsoft Active Directory for example).
Note
A service user is associated with one tenant only.
When you create the keytab file, the password you specify for the service user is used to generate a key. A
setting on the service user also allows you to configure a key type to be derived and used for the encryption of
the Kerberos ticket. You have to provide this keytab file as well as the key type to the tenant administrator so
that he or she can configure SAP Cloud Platform Identity Authentication service.
Caution
The realm you specify to generate the keytab file has to be in capital letters.
Example
You can derive the key by using your Java installation. To derive the key, proceed as follows:
1. In the command prompt, run the ktab -help command to see the list of available commands.
Tip
Go to your Java bin folder or set the Java path as an environment variable.
3. Register a service principal name (SPN) associated with the service user for the host name used to access
Identity Authentication. The SPN has to be unique.
Example
The command line setspn -A HTTP/<tenantID>.accounts.ondemand.com <service user>
registers an SPN for the <tenantID>.accounts.ondemand.com host associated with the service user.
Context
Procedure
1. Extract the key from the keytab file provided by the domain administrator.
Example
You can extract the key by using your Java installation.
1. In the command prompt, run the ktab -help command to see the list of available commands.
Tip
Go to your Java bin folder or set the Java path as an environment variable.
2. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Note
The realm (domain) has to be in capital letters.
○ Key type
The key type has to match the encryption type of the corresponding service user that contains the tenant
as a service principal name. Identity Authentication supports the following key types: RC4, AES128 and
AES256. For more information about these key types, see RFC 4757 and RFC 3962.
Note
By default the field is empty, which means any client IP is allowed.
Example
Enter 123.45.67.1/24, 189.101.112.1/16 to allow the Web client to use any client IP starting with
123.45.67 or with 189.101.
If the operation is successful, you receive the message SPNEGO settings saved.
Next Steps
Enable Kerberos authentication for specific applications. For more information, see Enable or Disable Kerberos
Authentication for an Application [page 47].
Overview
In the IdP-Initiated single sign-on (SSO), the authentication starts at the identity provider (IdP). The service
provider metadata that is used to configure the trust must contain the default assertion consumer service (ACS)
endpoint that can process unsolicited SAML responses. With SAP Cloud Platform, the endpoint is the application
protected URL.
Note
The following table lists the URL parameters you can use for IDP-initated SSO.
Example
User Richard Wilson would like to initiate an SSO process at the cloud identity provider and has configured the
default assertion consumer service (ACS) endpoint correctly. He tries to access the identity provider, but
because he does not have a valid session and is prompted to provide credentials. Once Richard has logged in at
the IdP, a session is created for him and he is automatically redirected to his application (the default ACS URL
as specified in the service provider (SP) metadata)).
Prerequisites
You have specified the default assertion consumer service (ACS) endpoint in the configuration of a trusted service
provider (SP) in the administration console for SAP Cloud Platform Identity Authentication service. For more
information, see Configure a Trusted Service Provider [page 35].
Context
By default, IDP-Initiated SSO is enabled in Identity Authentication. The tenant administrator can disable the IdP-
Initiated SSO process via the administration console for Identity Authentication.
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Passwords for the authentication of users are subject to certain rules. These rules are defined in the password
policy. SAP Cloud Platform Identity Authentication service provides you with two predefined password policies, in
addition to which you can create and configure a custom one.
● Standard
(Predefined) Use this option to set special rules for changing, resetting, and locking a password.
Note
This is the default setting. It meets the minimum strength requirements.
● Enterprise
(Predefined) Use this option to set enhanced password management features. It is stronger than the
standard policy, but weaker than the custom one.
● Custom
(Configurable) Use this option to set the strongest password management features for the password policy.
Remember
This option is only possible if you have configured a custom password policy in the administration console
for Identity Authentication. For more information, see Configure Custom Password Policy [page 106].
Password locked period Yes, 1 hour Yes, 1 hour Yes, minimum 1 hour, maxi
mum 24 hours
Indicates how long a pass
word is locked for.
Password history No Yes, the last 5 passwords are Yes, minimum the last 5 pass
retained. words, and maximum the last
Indicates whether a password
20 passwords are retained.
history is retained, and how
many passwords from the
history are retained.
● Set a password policy for an application. For more information, see Set a Password Policy for an Application
[page 104].
● Create a custom password policy. For more information, see Configure Custom Password Policy [page 106].
● Delete a custom password policy. For more information, see Delete Custom Password Policy [page 108].
Context
As a tenant administrator, you can set a password policy that matches your application logon requirements. You
can choose from standard, enterprise, and custom password policies. The standard and enterprise password
policies are predefined, and you cannot configure them. You can configure only the custom password policy. The
strength of the policies grows from standard to custom. For more information about the password policies
features, see Password Policies [page 102].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Once the application has been updated, the system displays the message Application <name of
application> updated.
Note
When the user tries to log on to the application whose password policy has been updated, he or she is
prompted to change the password if the current one does not meet the requirements in the updated
password policy.
Tenant administrators can create and configure a custom password policy for scenarios where SAP Cloud
Platform Identity Authentication service is the authenticating authority.
Context
Identity Authentication provides you with two predefined password policies, in addition to which you can create
and configure a custom one. The custom password policy is by default stronger than the enterprise policy, which
in turn is stronger than the standard policy.
Remember
You can only create one custom password policy. To change the configuration of the custom password policy
or to create a new one, delete the existing custom policy first, and then create the new one. For more
information, see Delete Custom Password Policy [page 108].
To create and configure a new custom password policy, follow the procedure:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Remember
The fields accept rules that are stronger than the enterprise password policy.
Password Policy Name The name of the password policy that appears in the admin
istration console.
Password Length The length can be between 8 and 255 characters. The de
fault value is 8 characters.
Password Lifetime The lifetime can be between 1 month and 6 months. The de
fault value is 6 months.
Maximum Duration of User Inactivity The maximum duration of user inactivity can be between 1
and 6 months. The default value is 6 month.
Number of Last Used Passwords that Cannot Be Reused The minimum requirement is the last 5 passwords to be re
tained. The value cannot be more than 20.
Number of Allowed Failed Logon Attempts The number of allowed failed logon attempts can be be
tween 1 and 5. The default value is 5.
Password Locked Period The period can be between 1 and 24 hours. The default
value is 24 hours.
Once the password policy has been created and configured, the system displays the message Password
policy <name of policy> created.
The new custom password policy appears in the list of the password policies that you can use for the
applications.
Next Steps
To use the custom password policy for your application or applications, you should set it as a password policy for
that application or applications. For more information, see Set a Password Policy for an Application [page 104].
Prerequisites
● You have created a custom password policy in the administration console for SAP Cloud Platform Identity
Authentication service. For more information, see Configure Custom Password Policy [page 106].
● The custom password policy should not be set as a password policy for any of the applications in the tenant.
For more information about how to set a standard or enterprise policy for an application, see Set a Password
Policy for an Application [page 104].
Context
You can only have one custom password policy for your tenant. To change the configuration of the custom
password policy, or to create a new one, delete the existing custom policy first.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Caution
You can only delete the password policy if it is not set as a password policy for any applications in the
tenant.
Once the password policy has been deleted, the system displays the message Password policy <name of
policy> deleted.
Initially, administration console for SAP Cloud Platform Identity Authentication service displays a default privacy
policy.
To set a new customized policy, you first need to create one and then to configure the versions for each language,
as you need to upload a plain text file for each language version.
Every time you want to update the privacy policy document you have to create a new document and to add its
language versions.
● English
● German
● Spanish
● French
● Japanese
● Korean
● Dutch
● Polish
● Portuguese
● Russian
● Chinese
● Italian
● Welsh
● Hebrew
Note
If the SP is configured to support a specific language, only this language is used by the application.
Note
The application takes the browser language only if the SP's language is not selected, and the locale
parameter is not set in the URL. The default browser setting is English.
Context
Provided you have the authorization, you can create and configure a new privacy policy. After you create a new
privacy policy document, you have to add custom language versions of the document. To set the custom
language versions, you need to upload text files for the respective languages.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The name can contain only Latin letters, numbers or the underscore character, or a combination of them.
Once the document has been created, the system displays the message Privacy policy document
<name of document> created.
Add the new custom versions for the languages. For more information, see Add Language Versions of a Privacy
Policy Document [page 111].
Related Information
To add a language version of a privacy policy document, you need to upload a plain text file containing the privacy
policy text.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Tip
Type the name of the document in the search field to filter the list items.
Once the file has been uploaded, the system displays the message Privacy policy file uploaded.
Related Information
Context
The privacy policy is displayed on the registration form, which form appears when the user chooses the Register
Now link on the login page. It is also shown to the user when the registration information has been upgraded.
Initially, the application is set to use a default privacy policy on the registration and upgrade forms. To change this
configuration, you have to select a custom privacy policy.
If you have the authorization, you can create a custom privacy policy document. This document is used once you
have set it for the respective application.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Related Information
Initially, administration console for SAP Cloud Platform Identity Authentication service displays default terms of
use. To set custom terms of use, you need to create a new document and to add its language versions.
Every time you want to update the terms of use document you have to create a new document and to add its
language versions.
For each language version, you have to upload a text file. You can define a terms of use document in the following
languages:
● English
● German
● Spanish
● French
● Japanese
● Korean
● Dutch
● Polish
● Portuguese
● Russian
● Chinese
● Italian
● Welsh
● Hebrew
Note
If the SP is configured to support a specific language, only this language is used by the application.
Note
The application takes the browser language only if the SP's language is not selected, and the locale
parameter is not set in the URL. The default browser setting is English.
Related Information
Context
Provided you have the authorization, you can create and configure a new terms of use document. After you create
the document, you have to add custom language versions of the document. To set the custom language versions,
you need to upload text files for the respective languages.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The name can contain only Latin letters, numbers or the underscore character, or a combination of them.
Once the document has been created, the system displays the message Terms of use document <name
of document> created.
Next Steps
Add the new custom versions for the languages. For more information, see Add Language Versions of a Terms of
Use Document [page 115].
Related Information
To add a language version of a terms of use document, you need to upload a UTF-8 encoded plain text file
containing the terms of use statement.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Tip
Type the name of the document in the search field to filter the list items.
Note
Use a file with an extension .txt.
Once the file has been uploaded, the system displays the message Terms of use file uploaded.
Related Information
Context
The terms of use document is displayed on the registration form, which form appears when the user chooses the
Register Now link on the login page. It is also shown to the user when the registration information has been
upgraded. By default, the application is set not to use a terms of use document on the registration and upgrade
forms. To change this configuration, you have to update the None setting in the administration console.
If you have the authorization, you can create a custom terms of use document. This document is used once you
have set it for the respective application.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Related Information
Tenant administrators can manage user accounts via the administration console of SAP Cloud Platform Identity
Authentication service, and via APIs.
The user management enables you to create, modify and delete users and their attributes, and manage the user
accounts in the user store of Identity Authentication.
Note
For more information about the users that are authenticated with their corporate credentials from the
corporate user store, see Corporate User Store [page 82].
Table 31:
Create user Create users via the Add User option in Create a New User [page 119]
the administration console
Create users via a CSV file import in the Import or Update Users for a Specific
administration console Application [page 68]
Create users programmatically via API Create User Resource [page 218]
Search users Search users in the administration con Search Users [page 120]
sole
List and edit user details List a specific user and edit the informa List and Edit User Details [page 122]
tion about that user via the administra
tion console
List and update user details via API ● User Resource [page 212]
● Update User Resource [page 226]
Update user details via a CSV file import Import or Update Users for a Specific
Application [page 68]
Delete users Delete users via the administration con Delete Users [page 123]
sole
Delete users programmatically via API Delete User Resource [page 234]
Manage the user group assignment Assign and unassign groups via the ad ● Assign Groups to a User [page 129]
ministration console ● Unassign Users from Groups [page
130]
As a tenant administrator, you can create a new user in the administration console for SAP Cloud Platform
Identity Authentication service.
Prerequisites
You are assigned the Manage Users role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Context
The tenant administrator creates the new user with a minimum set of attributes and can set an initial password.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
The system displays the first 20 users in the tenant sorted by their user ID number.
3. Press Add User.
4. Fill in the required fields in the pop-up window.
5. Select one of the following options:
Option Description
Send activation e-mail The user receives an e-mail with instructions how to activate the user account.
Set password The tenant administrator sets the password for the user.
Note
The user is prompted to reset the password during the first authentication.
As a tenant administrator, you can search for a specific user or users in the administration console for SAP Cloud
Platform Identity Authentication service
Prerequisites
You are assigned the Manage Users role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Context
You can list all users in the tenant for Identity Authentication or filter your search by User ID, First Name, Last
Name, E-Mail, or Login Name.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
The system displays the first 20 users in the tenant sorted by their user ID number.
3. Optional: You can choose one of the following:
Option Description
Note
This option is available only if the users in the tenant are more than 20.
Type your search Once the search is completed, the system will list the users whose User ID, E-Mail or Login Name
criteria string in match your search criteria string. In this case the system does not include the First Name and Last
the search field Name fields in the search.
and press the Enter
If you are not satisfied with the search result, edit your search criteria and repeat the step again.
key
Note
The search is case insensitive and does not require exact matching.
The wildcard search is enabled by default and you should not include the wildcard character as
terix (*) in your search criteria. If you place asterix (*) anywhere in your search string, except at
the end, the system will include that character in the search. Asterix (*) placed at the end of the
search string is ignored by the system.
Press Advanced The system checks the search fields simultaneously, and once the search is completed, it will list
Search and type the users that match the search criteria from all the fields.
your search criteria
strings in at least Note
one of the search
The search is case insensitive and does not require exact matching.
fields
The wildcard search is enabled by default and you should not include the wildcard character as
terix (*) in your search. If you place the asterix (*) character anywhere in your search string, in
cluding at the end of the string, the system will include it in the search. For example, if you type
*on in the First Name field, the system will look for users whose first three letters of the first
name are *on.
Related Information
As a tenant administrator, you can view detailed information about the users in the administration console for
SAP Cloud Platform Identity Authentication service. Optionally you can edit this information.
Procedure
For more information about how to find a user in Identity Authentication, see Search Users [page 120].
2. Click the user to view his or her details.
b. Press the icon next to the Personal Information, Employee Information, or Company Information
sections.
Note
a. Edit the information in the relevant fields and save your changes.
Note
Last Name, Display Name, and E-Mail fields are mandatory.
E-Mail and Login Name can be used as unique identifiers. Be sure to enter unique values if you edit
these two fields.
If you choose Customer, Employee, or Partner for User Type, the Company Relationship field is
overwritten, and takes the same value as in the User Type field. If you choose Public for User Type,
the Company Relationship can be filled with any of the options from the drop down list.
If the operation is successful, the system displays the message User <user ID> updated.
4. Optional: Choose the Applications tab, to view details specific for the applications that the user has logged on,
and the applications that the user was imported to via a CSV file import.
5. Optional: Choose the Legal tab to view audit information about the user, such as the policies accepted by him
or her, the last log on, and password related information.
6. Optional: Choose the Authentication tab to manage the two-factor authentication for the user.
You can see whether the user has enabled two factor authentication. If enabled you have two options:
○ Deactivate the user devices. For more information, see Deactivate User Devices for Two-Factor
Authentication [page 124].
○ Unlock the user passcode when the user needs to log on to the application before the automatic unlock
time. For more information, see Unlock User Passcode [page 124].
7. Optional: Choose the User Groups tab to manage the group assignments of the user.
You can see the user groups assigned to the user. You have two options:
○ Assign groups. For more information, see Assign Groups to a User [page 129].
○ Unassign one or more groups that are assigned to the user Unassign Users from Groups [page 130].
As a tenant administrator, you can delete users in the administration console for SAP Cloud Platform Identity
Authentication service
Procedure
For more information about how to find a user in Identity Authentication, see Search Users [page 120].
2. Select the checkbox next to the user or users that you want to delete.
This document shows you how to deactivate the mobile devices used by a user to generate passcodes for access
to applications requiring two-factor authentication. You deactivate the user mobile devices from the
administration console for SAP Cloud Platform Identity Authentication service
Context
You deactivate all user's mobile devices that generate passcodes if a single device has been lost or stolen. You
cannot deactivate a single device.
Note
If you deactivate the mobile devices, the user will no longer be able to log on to applications that require
passcodes. To be able to access them again the user has to activate a new mobile device on the user profile
page. For more information, see the Related Information.
Procedure
For more information about how to find a user in Identity Authentication, see Search Users [page 120].
2. Select the user whose device you want to deactivate.
3. Under Authentication choose Two-Factor Authentication.
4. Use the slider next to Status to deactivate two-factor authentication.
You can unlock a user passcode when the user needs to log on to the application before the automatic unlock
time, which is 60 minutes, has passed.
Context
The user locks his or her passcode after submitting five incorrect passcodes when trying to log on to an
application that requires two-factor authentication. The passcode is unlocked automatically after 60 minutes.
Procedure
For more information about how to find a user in SAP Cloud Platform Identity Authentication service, see
Search Users [page 120].
2. Select the user that you want to unlock.
Note
You can only unlock locked user passcodes.
Tenant administrators can create user groups, and assign and unassign groups to users via the administration
console for SAP Cloud Platform Identity Authentication service.
A user group is a collection of users. Groups serve to create sets of users who have something in common, for
example, users who work in the same department or users who have similar tasks in a company.
Table 32:
How to list the user groups in the tenant List User Groups [page 127]
How to list users in a user group List Users in User Groups [page 128]
Create a new user group Create a New User Group [page 126]
Add a user to a user group via CSV file Import or Update Users for a Specific Application [page 68]
Assign groups to a user via the administration console for Assign Groups to a User [page 129]
Identity Authentication
Unassign groups via the administration console for SAP Cloud Unassign Users from Groups [page 130]
Platform Identity Authentication service
Delete groups via the administration console for SAP Cloud Delete User Groups [page 131]
Platform Identity Authentication service.
As a tenant administrator you can create new user groups in the tenant via the administration console for SAP
Cloud Platform Identity Authentication service.
Prerequisites
You are assigned the Manage Groups role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Caution
The name field can contain lower-case Latin characters (a-z), upper-case Latin characters (A-Z), base 10
digits (0-9), hyphens, and underscores.
As a tenant administrator, you can list and view information about the user groups in a tenant in the
administration console for SAP Cloud Platform Identity Authentication service.
Prerequisites
● You are assigned the Manage Groups role. For more information about how to assign administrator roles, see
Edit Administrator Authorizations [page 146].
● You have created user groups in your tenant. For more details how to create user groups, see Create a New
User Group [page 126].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
As a tenant administrator, you can list and view information about the users in a user group in a tenant in the
administration console for SAP Cloud Platform Identity Authentication service.
Prerequisites
● You are assigned the Manage Groups role. For more information about how to assign administrator roles, see
Edit Administrator Authorizations [page 146].
● You have created at least one user group in the tenant. For more details about how to create user groups, see
Related Information.
● You have assigned at least one user to the selected user group. For more details about how to assign groups
to a user, see Related Information.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Related Information
As a tenant administrator, you can assign one or more groups created for a specific tenant to a user via the
administration console for SAP Cloud Platform Identity Authentication service.
Prerequisites
You have created user groups in your tenant. For more details how to create user groups, see Related
Information.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
The system displays the first 20 users in the tenant sorted by their user ID number.
3. Choose the user that you want to assign to a group or groups.
4. Choose the User Groups tab.
Next Steps
Configure the attributes that are sent to the application in the SAML 2.0 assertion. For more information, see
Configure the User Attributes Sent to the Application [page 38]
Related Information
As a tenant administrator, you can unassign one or more groups that are assigned to a user via the administration
console for SAP Cloud Platform Identity Authentication service.
Prerequisites
● You have created user groups in your tenant. For more details how to create user groups, see Related
Information.
● You have assigned groups to the user. For more details how to assign a group or groups to a user, see Related
Information.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
The system displays the first 20 users in the tenant sorted by their user ID number.
3. Choose the user whose group assignments you want to edit.
4. Choose User Groups tab.
5. Select the group or groups that you want to unassign.
6. Press the Unassign Groups button at the bottom of the page.
7. Confirm your changes.
Related Information
As a tenant administrator, you can delete one or more user groups in a tenant of SAP Cloud Platform Identity
Authentication service.
Prerequisites
You are assigned the Manage Groups role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Context
The Delete User Groups operation removes user groups and unassigns all users from them.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
3. Choose the icon in the left-hand panel to enter Delete Groups mode.
If the operation is successful, the system displays the message <number> groups deleted.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
If the operation is successful, the system displays the message 1 group deleted.
As a tenant administrator, you can configure target systems for user provisioning and provision users to these
target systems.
Related Information
Configure SAP Jam Target Systems for User Provisioning [page 138]
Provision Users to SAP Jam Target Systems [page 133]
Delete SAP Jam Target System [page 140]
Tenant administrators can provision SAP Cloud Platform Identity Authentication service users to SAP Jam targets
systems.
Prerequisites
● You are assigned the Manage Users role. For more information about how to assign administrator roles, see
Edit Administrator Authorizations [page 146].
● You have configured a target system in the administration console for Identity Authentication. For more
details about how to configure target systems, see Configure SAP Jam Target Systems for User Provisioning
[page 138].
Note
Currently, Identity Authentication only supports user provisioning to SAP Jam instances.
Context
Identity Authentication supports the following scenarios for user provisioning to SAP Jam target systems:
The users that are in the user store of Identity Authentication are provisioned to the SAP Jam target system with a
certain set of attributes. The table below shows the attributes taken from Identity Authentication and their
mapping to the SAP Jam target system.
Table 33: Attribute Mapping Between SAP Cloud Platform Identity Authentication Service and SAP Jam
SAP Cloud Platform Identity Authentication Service Attrib SAP Jam Attribute
ute
Core Schema
firstName name.givenName
lastName name.familyName
uid userName
title jobFunction
userType type
mail emails.value
status active
Note
active is true only when status in SAP Cloud Platform
Identity Authentication service is equal to active. In the
other case active is false.
telephone phoneNumbers[work].value
street addresses[home].streetAddress
city addresses[home].locality
zip addresses[home].postalCode
country addresses[home].country
companyStreet addresses[work].streetAddress
companyCity addresses[work].locality
companyZip addresses[work].postalCode
companyCountry addresses[work].country
locale locale
Note
The locale must be of the format ll_CC where:
Caution
Do not send locale if language or country user at
tribute is missing.
employeeNumber personnelNumber
costCenter costCenter
organization company
division division
department department
Note
If Identity Authentication is used as proxy to delegate the authentication to a corporate identity provider, the
users that are authenticated by the corporate identity provider will not be provisioned during authentication.
When you delete a user, he or she is automatically deprovisioned from the configured target systems.
To provision users, choose one of the options below and follow the corresponding procedure.
Context
The tenant administrator can select the target systems that all users will be provisioned to.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
If you do not have a configured target system in your list, you can add one. For more details, see Configure
SAP Jam Target Systems for User Provisioning [page 138].
4. Press Provision.
If the operation is successful, the system displays the message <number of users> provisioned.
Context
The tenant administrator can choose which of the users to be provisioned to the configured target systems.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
The system displays the first 20 users in the tenant sorted by their user ID number.
3. Optional: You can choose one of the following:
Option Description
Note
This option is available only if the users in the tenant are more than 20.
Type your search Once the search is completed, the system will list the users whose User ID, E-Mail or Login Name
criteria string in match your search criteria string. In this case the system does not include the First Name and Last
the search field Name fields in the search.
and press the Enter
If you are not satisfied with the search result, edit your search criteria and repeat the step again.
key
Note
The search is case insensitive and does not require exact matching.
The wildcard search is enabled by default and you should not include the wildcard character as
terix (*) in your search criteria. If you place asterix (*) anywhere in your search string, except at
the end, the system will include that character in the search. Asterix (*) placed at the end of the
search string is ignored by the system.
Press Advanced The system checks the search fields simultaneously, and once the search is completed, it will list
Search and type the users that match the search criteria from all the fields.
your search criteria
strings in at least Note
one of the search
The search is case insensitive and does not require exact matching.
fields
The wildcard search is enabled by default and you should not include the wildcard character as
terix (*) in your search. If you place the asterix (*) character anywhere in your search string, in
cluding at the end of the string, the system will include it in the search. For example, if you type
*on in the First Name field, the system will look for users whose first three letters of the first
name are *on.
4. Select the checkbox next to the user or users that you want to provision.
5. Press Provision Users.
6. Confirm the operation.
If the operation is successful, the system displays the message <number of users> provisioned.
For more information about how to configure Identity Authentication to use a corporate user store in addition to
its own user store, see Configure Connection to a Corporate User Store [page 84].
All newly created and updated users are automatically provisioned to the target systems configured in the
administration console for Identity Authentication. The users that use the self-registration service will be
automatically provisioned to the target systems too.
For more information about user creation or user update, see Related Information
Related Information
Tenant administrators can configure SAP Jam target systems for user provisioning via the administration console
for SAP Cloud Platform Identity Authentication service.
Prerequisites
You are assigned the Manage Users role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Note
Currently, Identity Authentication only supports user provisioning to SAP Jam instances.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
If the operation is successful, the system displays the message System <name of system>
configuration updated.
7. (Optional) To check the SAP Jam Target System configuration press the Test Connection button.
If the operation is successful, the system displays the message Connection to the selected target
system was established successfully.
Note
To change the configuration, select the target system, press Edit, fill in the fields with the new entries, and
save your changes.
As a tenant administrator, you can delete one or more SAP Jam target systems in a tenant of SAP Cloud Platform
Identity Authentication service.
Prerequisites
You are assigned the Manage Users role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Once the target system or systems have been deleted, the system displays the message <number> target
systems deleted.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Once the application has been deleted, the system displays the message 1 target system deleted.
This section describes how, as a tenant administrator, you can list all administrators in the administration console
for SAP Cloud Platform Identity Authentication Service, add new administrators, and edit the administrator
authorizations.
Related Information
As a tenant administrator, you can list the administrators and their authorizations in the administration console
for SAP Cloud Platform Identity Authentication service
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The list also includes the SAP Cloud Platform system, which by default has authorizations to set up the
trust with Identity Authentication. For more details, see Related Information.
3. Click on the name from the list item to view the profile details, such as user ID and e-mail, and the
authorizations assigned to the administrator.
Tip
Type the name of the administrator in the search field to filter the list items.
Related Information
As a tenant administrator, you can add new administrators in the administration console for SAP Cloud Platform
Identity Authentication service
Prerequisites
To add new tenant administrators, you must be assigned the Manage Tenant Configuration role.
Context
You can add both a person and a system in the administration console for Identity Authentication to act as
administrators. The system can receive the same roles and can perform the same actions as the human
administrator.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The list also includes the SAP Cloud Platform system, which by default has authorizations to set up the
trust with Identity Authentication. For more details, see Related Information.
The First Name, and Last Name fields will be prefilled automatically for users that already exist in system.
6. Assign the required administrator roles for the user.
To be a tenant administrator, a user must be assigned at least one of the following roles.
Manage Applications This role gives the tenant administrator permission to con
figure the applications via the administration console.
Manage Corporate Identity Providers This role gives the tenant administrator permission to con
figure the identity providers via the administration console.
Manage Users This role gives the tenant administrator permission to man
age, import and export users via the administration con
sole.
Manage Groups This role gives the tenant administrator permission to cre
ate, edit and delete user groups via the administration con
sole.
Manage Tenant Configuration This role gives the tenant administrator permission to man
age tenant configuration and authorization assignment to
users.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Note
The list also includes the SAP Cloud Platform system, which by default has authorizations to set up the
trust with Identity Authentication. For more details, see Related Information.
3. Press the +Add button on the left hand panel in order to add a new administrator to the list.
4. Choose Add System.
5. Enter the name of the system under Name.
6. Assign the required administrator roles for the system.
To be a tenant administrator, a user must be assigned at least one of the following roles.
Manage Applications This role gives the tenant administrator permission to con
figure the applications via the administration console.
Manage Corporate Identity Providers This role gives the tenant administrator permission to con
figure the identity providers via the administration console.
Manage Users This role gives the tenant administrator permission to man
age, import and export users via the administration con
sole.
Manage Groups This role gives the tenant administrator permission to cre
ate, edit and delete user groups via the administration con
sole.
Manage Tenant Configuration This role gives the tenant administrator permission to man
age tenant configuration and authorization assignment to
users.
7. Configure the method for authentication when the system is used. You can choose from the following two
options:
○ Certificate
○ Password
Note
User ID and password are used for basic authentication when Identity Authentication is used. The user
ID is generated automatically when you set the password for the first time.
As a tenant administrator, you can edit both your own authorizations and other administrators' authorizations in
the administration console for SAP Cloud Platform Identity Authentication service
Prerequisites
To edit tenant administrators' authorizations, you must be assigned the Manage Tenant Configuration role.
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
The list also includes the SAP Cloud Platform system, which by default has authorizations to set up the
trust with Identity Authentication. For more details, see Related Information.
Tip
Type the name of the administrator in the search field to filter the list items.
Manage Corporate Identity Providers This role gives the tenant administrator permission to
configure the identity providers via the administration
console.
Manage Groups This role gives the tenant administrator permission to cre
ate, edit and delete user groups via the administration
console.
Manage Tenant Configuration This role gives the tenant administrator permission to
manage tenant configuration and authorization assign
ment to users.
If you remove all authorizations, the user will no longer be a tenant administrator, and the name will be
removed from the list on the left.
You cannot remove the Manage Tenant Configuration role from your own user.
If the operation is successful, the system displays the message Tenant administrator <name of
tenant administrator> updated.
Related Information
Initially, Identity Authentication is set as the default identity provider for the applications. This section describes
the scenarios in which Identity Authentication acts as a proxy to delegate the authentication to a corporate
identity provider.
An identity provider can function as a proxy for another identity provider. An identity provider proxy enables you
to create structures of trust relationships that ultimately simplify the management of your service providers.
There is no direct trust relationship between the authenticating identity provider and the service provider that the
user is trying to access.
Table 37:
How Identity Authentication can use a SAML 2.0 identity pro Configure Trust with Corporate Identity Provider [page 160]
vider as an external authenticating authority. Identity
Authentication acts as a proxy.
How to choose a type for the corporate identity provider Choose Identity Provider Type [page 163]
How to delete corporate identity providers Delete Corporate Identity Providers [page 164]
How to configure the Identity Federation option Configure Identity Federation with the User Store of SAP
Cloud Platform Identity Authentication Service [page 166]
How to configure your systems for IdP-Initiated SSO with a Configure IdP-Initiated SSO with Corporate Identity Providers
corporate identity provider [page 149]
How to redirect the user to specific URL after logout Service Provider Initiated Logout with Corporate Identity Pro
viders [page 158]
This use case is suitable for customers and partners who need to provide access to a cloud application for their
employees via their corporate identity providers. In this scenario, the authentication starts at the corporate
identity provider (IdP), with SAP Cloud Platform Identity Authentication service being in the role of an identity
provider proxy. As such, Identity Authentication will act as an SAML 2.0 identity provider to the service provider,
and as an SAML 2.0 service provider to the corporate identity provider or providers. Once a user is authenticated
at the corporate identity provider, successive authentication requests from the service provider which use the
same corporate identity provider will not be forwarded to it while the session at Identity Authentication is active.
Identity Authentication will issue assertions based on the user data received during the first authentication.
For this scenario, the configurations are made by users with different roles in different systems.
Tenant administrator Tenant of Identity ● Authenticating identity 2. Configure SAP Cloud Plat
providers form Identity Authentication
Authentication
● (Optional) Request Service [page 153]
Multiple Corporate IdP
Trust feature
Tenant administrator Tenant of Identity (Optional) Access to users 4. Optional: Configure Addi
tional Settings in SAP Cloud
Authentication
Platform Identity Authentica
tion Service [page 155]
For more information about the configuration steps, follow the links in the table or see the sections below.
Prerequisites
The IDP-Initiated SSO option in the tenant of Identity Authentication must be enabled.
Note
IDP-Initiated SSO is enabled by default in Identity Authentication. For more information about how the tenant
administrator can enable or disable this option, see Configure IdP-Initiated SSO [page 99].
Context
As an administrator of the application, you have to configure SAP Cloud Platform Identity Authentication service
as a trusted identity provider for the application.
Note
To do this, you will need the SAML 2.0 metadata of Identity Authentication. To receive the metadata, contact
the tenant administrator of Identity Authentication.
Send the metadata of the service provider to the administrator of Identity Authentication. This is required for
setting up the trust on the Identity Authentication provider side.
Context
In the scenario where SAP Cloud Platform Identity Authentication service acts as an identity provider proxy, it is in
the role of an identity provider for the application, and a service provider for the corporate identity provider. You
should configure trusts with the service provider and the corporate identity provider.
Procedure
1. Configure trust with the service provider via the administration console. For more information, see Configure
a Trusted Service Provider [page 35]
For this procedure, you will need the metadata from the service provider. If you do not have this, contact the
administrator of the application.
The service provider metadata that is used to configure the trust must contain the default assertion
consumer service (ACS) endpoint that can process unsolicited SAML responses. With SAP Cloud Platform,
the endpoint is the application protected URL.
2. Configure a trust with the corporate identity provider. For more information, see Configure Trust with
Corporate Identity Provider [page 160].
For this procedure, you will need the metadata from the corporate identity provider. If you do not have this,
contact the administrator of the corporate identity provider.
3. You have the following options:
○ If your scenario includes more than one corporate identity provider, request the Multiple Corporate IdP
Trust feature from an Identity Authentication operator.
Note
To do this, create a ticket on SAP Support Portal under component BC-IAM-IDS with the following
headline "Enable Multiple Corporate IdP Trust feature for tenant <tenant_id>".
Next Steps
1. Send the Entity ID of the service provider to the administrator of the corporate identity provider. The
administrator needs this information for the consumer assertion endpoint configuration.
Tip
2. Send the metadata of the tenant of Identity Authentication to the administrator of the service provider and
the administrator of the corporate identity provider. They need the metadata for the trust configurations of
the systems. For more information about how to download the tenant metadata, see Tenant SAML 2.0
Configuration [page 76].
Context
The following configuration is made by the administrator of the corporate identity provider.
Procedure
Note
To do this, you will need the SAML 2.0 metadata of Identity Authentication. If you do not have this, contact
the tenant administrator of Identity Authentication.
Tip
For more information about how to register Identity Authentication as a service provider, consult the
corporate identity provider documentation. If the corporate identity provider is also a tenant of Identity
Authentication, see Configure a Trusted Service Provider [page 35].
Tip
The ACS endpoint URL should have the following format: https://<the current ACS endpoint
URL>?sp=<sp_name>. Request the Entity ID of the service provider from the tenant administrator of
Identity Authentication.
Results
Once the trust is configured, the user can access the application via the link sent by the corporate identity
provider administrator. For more information about how to configure the link for the IdP-initiated SSO scenario,
consult the corporate identity provider documentation.
Tip
If your corporate identity provider is Identity Authentication, the link for IdP-Initiated SSO follows the pattern:
https://<tenant_ID>.accounts.ondemand.com/saml2/idp/sso?
sp=<sp_name>[&RelayState=<sp_specific_value>&index=<index_number>]. In this use case, replace the
sp_name with the Entity ID of the tenant of Identity Authentication acting as the service provider. The
RelayState and index parameters are not mandatory and can be skipped. For more information about the
configuration, see Configure IdP-Initiated SSO [page 99].
Next Steps
Send the metadata of the corporate identity provider to the administrator of Identity Authentication. This will be
needed for setting up the trust.
Context
The following configurations are made by the tenant administrator of SAP Cloud Platform Identity Authentication
service.
Context
This configuration allows you to restrict access to the application to users who are in the Identity Authentication
user store. Users who are not in the user store of Identity Authentication will not be able to access the application.
Procedure
1. Import the users that you will grant access to the application to via a CSV file import.
For more information about how to import users in Identity Authentication, see Import or Update Users for a
Specific Application [page 68].
2. Switch on the identity federation option in the administration console. For more information, see Configure
Identity Federation with the User Store of SAP Cloud Platform Identity Authentication Service [page 166].
This option allows the application to check if the users authenticated by the corporate identity provider exist
in the user store of Identity Authentication.
Results
Only users that are in the user store of Identity Authentication will be able to access the application. If a user is not
part of the user store of Identity Authentication, this user receives the following message: Sorry, but you are
currently not authorized for access.
The settings in the application configuration for assertion attributes and name ID attribute will be used for issuing
the assertion. For more information, see Configure the User Attributes Sent to the Application [page 38]and
Configure the Name ID Attribute Sent to the Application [page 41].
Context
This configuration allows you to restrict the access to the application only to users who belong to certain user
groups. This option is suitable for scenarios with more than one corporate identity providers. The tenant
Procedure
1. Make sure that the required user groups are created in the administration console of Identity Authentication.
For more information, see Create a New User Group [page 126].
2. Import the users that you will grant access to the application via a CSV file import.
Caution
The groups in the Groups column in your CSV file must match the groups that you created via the
administration console.
For more information about how to import users in Identity Authentication, see Import or Update Users for a
Specific Application [page 68].
3. Switch on the identity federation option in the administration console, and assign user groups to the
corporate identity provider. For more information, see Configure Identity Federation with the User Store of
SAP Cloud Platform Identity Authentication Service [page 166].
Results
Only the members of these groups will be authorized to access applications after successful authentication. If a
user is not part of the groups, this user receives the following message: Sorry, but you are currently not
authorized for access.
Context
When the identity federation feature is disabled, Identity Authentication sends to the application the same
attributes it has received from the corporate identity provider.
When the identity federation feature is enabled, Identity Authentication checks if a user with the respective unique
identifier, written in the NameID attribute in the assertion coming from the corporate identity provider, exists in
the user store of Identity Authentication. The following options exists:
● If the user exists, Identity Authentication issues a new assertion with Name ID and assertion attributes,
configured for the application.
● If the user does not exist in the user store of Identity Authentication this user receives the following message:
Sorry, but you are currently not authorized for access.
If you want the application to receive assertions and name ID attributes that are different from those sent by the
corporate identity provider, do the following: Configure the User Attributes Sent to the Application [page 38] and
Configure the Name ID Attribute Sent to the Application [page 41].
Procedure
1. Switch on the identity federation option in the administration console. For more information, see Configure
Identity Federation with the User Store of SAP Cloud Platform Identity Authentication Service [page 166].
2. Configure the user attributes and Name ID attribute sent to the application. For more information, see:
Results
The application will receive in the assertion the attributes and name ID attribute that you have configured in
Identity Authentication They will be different from those that the corporate identity provider sent to Identity
Authentication.
In this scenario, SAP Cloud Platform Identity Authentication service has to be configured as an identity provider
proxy. The corporate identity provider acts as an authenticating IdP to the application.
The logout procedure is triggered by the user at the service provider and results in a logout request sent to the
identity provider proxy. Consequently, the identity provider proxy processes the request and destroys any local
session information about the user. The identity provider proxy then checks whether there are other service
providers in the single sign-on (SSO) session and sends logout requests to all of them. In return, the service
providers send logout responses to the identity provider proxy informing it that the logout process is successful.
Finally, the identity provider proxy sends a logout response to the original requesting service provider or the
service provider of the application, and this procedure completes the logout process.
As an additional option, the tenant administrator of Identity Authentication can configure a URL which is sent in
the SAML 2.0 Logout Response as an extension and can be used to redirect the users after logging out of the
application. The URL is specific for each corporate identity provider with which Identity Authentication has
established a trust. For more information about this option, see Configure Logout URL [page 159].
When Identity Authentication acts as a proxy to delegate authentication to an external corporate identity provider,
and the user who is logged on to one or more applications chooses the Log Out link in one of the applications, the
following flow is in force:
Prerequisites
Identity Authentication must be configured to act as an identity provider proxy to delegate the authentication to a
corporate identity provider. For more information, see Configure Trust with Corporate Identity Provider [page
160].
Context
When the user logs out of an application via a service provider initiated logout he or she can be redirected to a
specific URL. This configuration can be applied to scenarios with one or more corporate identity providers. You
configure a specific redirect URL in the administration console for Identity Authentication for each corporate
identity provider.
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
○ If you do not have an identity provider in your list, choose the Add button to create one, and proceed with
the configuration.
○ If you have an identity provider in your list, choose the one that you want to edit.
Tip
Type the name of the identity provider in the search field to filter the list items.
Results
Once the user has logged out of the application, Identity Authentication sends the logout URL in the SAML 2.0
Response as an extension to the application. The logout URL can be used by the application to redirect the user to
the URL configured for the corporate identity provider in the administration console for Identity Authentication
This document is intended to help you configure trust with a corporate identity provider in the administration
console for SAP Cloud Platform Identity Authentication service. In this scenario Identity Authentication acts as a
proxy to delegate the authentication to the corporate identity provider.
Prerequisites
● You are assigned the Manage Corporate Identity Providers role. For more information about how to assign
administrator roles, see Edit Administrator Authorizations [page 146].
Note
If you want to use IdP initiated single sign-on (SSO) from your corporate identity provider, you have to add
the parameter sp=<sp_name> to the assertion consumer service (ACS) endpoint configured on your
corporate identity provider side for Identity Authentication.
Example
https://<tenant_ID>.accounts.ondemand.com/saml2/idp/acs?sp=<sp_name>
sp is the name of the SAML 2 service provider for which SSO is performed.
To see how to download the SAML 2.0 metadata of Identity Authentication read Tenant SAML 2.0
Configuration [page 76].
● You have downloaded the corporate identity provider metadata. For more information, see the
documentation provided by the corporate identity provider.
Context
Identity Authentication can use a SAML 2.0 identity provider as an external authenticating authority. Identity
Authentication thus acts as a proxy to delegate authentication to the external corporate identity provider. The
requests for authentication sent by a service provider will be forwarded to the corporate identity provider.
As an identity provider proxy, Identity Authentication will act as an SAML 2.0 identity provider to the service
provider, and as an SAML 2.0 service provider to the corporate identity provider. Once a user is authenticated at
the corporate identity provider, successive authentication requests from service providers which use the same
corporate identity provider will not be forwarded to it as long as the session at Identity Authentication is active.
Identity Authentication will issue assertions based on the user data received during the first authentication.
To use Identity Authentication as a proxy to delegate authentication to an external corporate identity provider you
have to configure trust with that corporate identity provider. To configure a trusted corporate identity provider,
proceed as follows:
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
○ If you do not have an identity provider in your list, choose the Add button to create one, and proceed with
the configuration.
○ If you have an identity provider in your list, choose the one that you want to edit.
Tip
Type the name of the identity provider in the search field to filter the list items.
Note
Use a file with an extension .xml.
When the identity provider metadata is uploaded, the fields are populated automatically with the parsed data
from the XML file. The minimum configuration is to complete the Name field, add at least one single sign-on
endpoint, and provide a signing certificate.
Field Description
Single Sign-On Endpoint URL The URL of the identity provider single sign-on endpoint
that receives authentication requests.
Single Logout Endpoint URL The URL of the identity provider's single logout endpoint
that receives logout messages.
Once the identity provider has been updated, the system displays the message Identity provider <name
of identity provider> updated.
Next Steps
Select the configured identity provider as the authenticating identity provider for the application. For more
information, see Choose Identity Provider for an Application [page 73].
This topic shows you how to choose a type for the corporate identity provider.
Prerequisites
Context
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
○ If you do not have an identity provider in your list, choose the Add button to create one, and proceed with
the configuration.
○ If you have an identity provider in your list, choose the one that you want to edit.
Tip
Type the name of the identity provider in the search field to filter the list items.
Once the identity provider has been updated, the system displays the message Identity provider <name
of identity provider> updated.
Related Information
As a tenant administrator, you can delete one or more corporate identity providers in a tenant of SAP Cloud
Platform Identity Authentication service.
Prerequisites
● You have the Manage Corporate Identity Providers role. For more information about the different roles and
how to edit them, see Edit Administrator Authorizations [page 146].
● You have at least one corporate identity provider that you want to delete.
● The identity provider you want to delete must not be used by an application. For more information about how
to choose an identity provider for an application, see Choose Identity Provider for an Application [page 73].
Context
A Delete Identity Providers operation removes the identity providers and all of their configurations from the tenant
of Identity Authentication.
Note
If you want to delete an identity provider that is used as authenticating identity provider for an application, you
have to choose another authenticating identity provider for that application. For more information, see Choose
Identity Provider for an Application [page 73].
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
The system deletes only the identity providers that are not used by applications.
Once the identity provider or identity providers have been deleted, the system displays the message
<number> identity providers deleted.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Tip
Type the name of the identity provider in the search field to filter the list items.
4. Choose the Delete button in the right-hand panel to delete the selected corporate identity provider.
5. Confirm the operation in the pop-up dialog.
The system deletes only the identity provider that is not used by applications.
Once the identity provider has been deleted, the system displays the message Identity provider
deleted.
Related Information
Tenant administrators can configure identity federation with SAP Cloud Platform Identity Authentication service
user store.
Prerequisites
● You have the Manage Corporate Identity Providers role. For more information about how to assign
administrator roles, see Edit Administrator Authorizations [page 146].
● You have configured Identity Authentication to use a corporate identity provider as an external authenticating
authority. For more information, see Configure Trust with Corporate Identity Provider [page 160]
● You have selected the configured identity provider as the authenticating identity provider for your application.
For more information, see Choose Identity Provider for an Application [page 73].
● You have imported the users, authenticated by the corporate identity provider, in Identity Authentication. For
more information about how to import users, see Import or Update Users for a Specific Application [page 68].
Context
The Identity Federation option allows the application to check if the users authenticated by the corporate identity
provider exist in the Identity Authentication user store.
Remember
In scenarios when the application is using for authentication a corporate identity provider, and the Identity
Federation option is disabled, the user attributes, the name ID attributes, and the default attributes
configurations in the administration console for Identity Authentication are not relevant. In such scenarios,
Identity Authentication sends to the application the same attributes it has received from the corporate identity
provider. For more information about the corporate identity provider scenario, see Corporate Identity
Providers [page 148].
If Identity Federation is enabled, only the users that are imported in Identity Authentication are able to access the
application. For more information about how to enable or disable Identity Federation with Identity Authentication,
see the Enable Identity Federation with Identity Authentication User Store section in this topic.
If the Identity Federation option is enabled, the corporate identity provider will use the SAML attribute
configuration set for the service provider. To change the configuration, follow the procedure described in
Configure the Name ID Attribute Sent to the Application [page 41].
As a next step, when Identity Federation is enabled, you can assign a group or groups to the corporate identity
provider. Only users that are members of the assigned group can access the application. For more information
about how to assign or unassign user groups to corporate identity providers, see the Assign User Groups to
Corporate Identity Providers section in this topic.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
○ If you do not have an identity provider in your list, click the Add button to create one, and proceed with the
configuration.
○ If you have an identity provider in your list, choose the one that you want to configure.
4. Use the slider next to Identity Federation to disable or enable it.
If the operation is successful, the system displays the message Identity provider <name of identity
provider> updated.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
○ If you do not have an identity provider in your list, choose the Add button to create one, and proceed with
the configuration.
○ If you have an identity provider in your list, choose the one that you want to edit.
Tip
Type the name of the identity provider in the search field to filter the list items.
You will see a list of the user groups assigned to this corporate identity provider. If no groups are assigned, the
list will be empty.
5. Choose the Assign Groups button.
6. Select the groups that you want to assign to this corporate identity provider.
The list does not include the groups that are already assigned to the corporate identity provider.
If you do not have any user groups in your list, you can create one. For more details about how to create user
groups and assign the group to a user, see Related Information.
7. Save your changes.
If the operation is successful, the system displays the message Identity provider <name of identity
provider> updated.
Note
To unassign user groups, select the groups you want to unassign, choose the Unassign Groups button, and
confirm the operation in the dialog.
Users that belong only to the unassigned groups will not be able to access the application any more.
By configuring a social provider, users can log on to applications with their social media credentials by liking their
accounts in SAP Cloud Platform Identity Authentication service to the social media account.
Context
Identity Authentication uses the OAuth protocol for social sign-on via one of the following predefined social
providers:
● Twitter
● Facebook
● LinkedIn
● Google
Once a user has allowed Identity Authentication to link his or her account with the social provider accounts, the
user can log on to applications via the social providers.
To configure social identity provider for the tenant, you have to register new applications on the corresponding
social network sites. For more details, see Related Information.
Note
You need to type https://<tenant_domain>/ui/oauth/googleCallback in the Authorized redirect URIs
field when you create your client ID in Google Developers Console. For more information about the redirect
URIs for your OAuth 2.0 credentials, see Set a redirect URI .
Google's client ID The Google OAuth 2.0 credential after you set a project in the
Google Developers Console.
Google's client secret The Google OAuth 2.0 credential after you set a project in the
Google Developers Console.
Facebook's application secret The secret generated after you add an application on Face
book.
LinkedIn's Client ID (API key) The key generated by LinkedIn to identify a user application
and for API calls.
LinkedIn's Client Secret (API secret) The secret generated by LinkedIn to identify a user application
and for API calls.
Twitter's consumer key The key generated by Twitter to identify which user applica
tion is making the request.
Twitter's consumer secret The secret generated by Twitter to identify which user appli
cation is making the request.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Check for leading or trailing spaces in the authentication attributes fields, and delete them. Sign-on
through the social identity provider will not work if there are blank spaces before or after the strings in the
fields.
If the operation is successful, you will receive the following message: <Social Provider Name> updated.
The slider next to the social provider is switched to ON.
Note
If you do not want to use any of the social providers for log in you can drag the slider next to the social
provider to OFF. The configuration for this social provider will be preserved, but the social provider will not
appear on the login pages of the applications in the tenant.
If you want to remove the configuration for a given social provider, see Related Information for more
details.
Next Steps
The above configurations are valid for the whole tenant. They will take effect for a specific application if you enable
the Social Sign-On option via the administration console. For more information about how to enable social sign on
for a specific application, see Enable or Disable Social Sign-On for an Application [page 44].
Related Information
You can remove the configurations of the social providers in the administration of SAP Cloud Platform Identity
Authentication service.
Prerequisites
You have a configured social provider in the administration console for Identity Authentication
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Results
The configuration for the selected social provider will be removed. The social provider will not appear on the login
pages of the applications in the tenant.
Related Information
Context
The exported change logs are saved in a CSV file and contain information about CREATE, UPDATE, or DELETE
operations performed by administrators.
The change log entries are not deleted from the system. Each record should contain the following data:
● Date
The date when the resource was created, updated, or deleted.
● Administrator's ID
The ID of the user or the system that made the change.
● Administrator's Name
The name of the user or the system that made the change.
● Resource Type
This indicates which type of resource was created, updated, or deleted, for example service provider.
● Resource ID
An identifier for the resource.
● Resource Name
The name of the resource that was created, updated, or deleted.
● Action
○ CREATE
The log shows the value of the attribute when the resource was created.
○ UPDATE
The log shows the changed value of the attribute when the resource was updated.
○ DELETE
The log shows which resource was deleted.
● Attribute
The attribute of the resource that was created or updated with the relevant operation.
● Value
The new value of the attribute.
Note
There are attributes whose values cannot be displayed in the logs. In such cases the value fields are left
blank.
Example
The table shows change logs for the following operations:
16-05-2014 P123456 Donna Service 500964f6e sp.exam UPDATE Privacy Pol Company A
10:21:21 Moore Provider 4b0f3cba1 ple.com icy Privacy Pol
01f700 icy
16-05-2014 P123456 Donna Privacy Pol 53da05f9e English Ver CREATE Plain Text
10:06:24 Moore icy Docu 4b0732235 sion of Privacy Pol
ment f24b8e Company A icy File
Privacy Pol
icy
16-05-2014 P123456 Donna Privacy Pol 53da05f9e Company A CREATE Display Company A
10:05:11 Moore icy Docu 4b0732235 Privacy Pol Name Privacy Pol
ment f24b8a icy icy
16-05-2014 P123456 Donna Terms of 53da0595e English Ver CREATE Plain Text
10:03:18 Moore Use Docu 4b0732235 sion of Terms of
ment f24b04 Company A Use File
Terms of
Use
15-05-2014 P123456 Donna Service 500964f6e Company A UPDATE SAML 2.0 com
11:32:18 Moore Provider 4b0f3cba1 (com Provider pany_a_ser
01f700 pany_a_ser Name ¢¡ÁŁ©(µ»r`lÍ’ $v¼3R
¢¡ÁŁ©(µ»r`lÍ’ $v¼3R vider
vider)
15-05-2014 P123456 Donna Service 500964f6e Company A UPDATE Single Log serv
11:32:18 Moore Provider 4b0f3cba1 (com out End ¢¡Á−©"µ½rZlâ’$
VÃ
01f700 pany_a_ser point vider_slo_e
¢¡ÁŁ©(µ»r`lÍ’ $v¼3R ndpoint,
vider) HTTP-
POST
15-05-2014 P123456 Donna Service 500964f6e Company A UPDATE Single Log serv
11:32:18 Moore Provider 4b0f3cba1 (com out End ¢¡Á−©"µ½rZlâ’$
VÃ
01f700 pany_a_ser point vider_slo_e
¢¡ÁŁ©(µ»r`lÍ’ $v¼3R ndpoint,
vider) HTTP-Redi
rect
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Related Information
Prerequisites
You are assigned the Manage Users role. For more information about how to assign administrator roles, see Edit
Administrator Authorizations [page 146].
Context
You can download an CSV file containing information of up to 10,000 tenant users in SAP Cloud Platform Identity
Authentication service including the tenant administrators. The CSV file contains the following columns: status,
loginName, mail, firstName, and lastName. If the status of a user is inactive, he or she cannot perform any
operations on the tenant.
Example
A tenant administrator downloads a CSV file with the current users in the system. As a result, the administrator
receives the following information:
Table 44:
status loginName mail firstName lastName
All users but one can log on to tenant applications. Richard Wilson cannot log on because his user is not active.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Related Information
You can view statistical information for a tenant in the administration console for SAP Cloud Platform Identity
Authentication service
Context
The Reporting view displays a chart of statistical information with the number of the user logon requests per
month in the tenant.
A logon request is a single authentication request managed via Identity Authentication. Identity Authentication
counts only one logon request per user per day. Logon requests are independent of the authentication
mechanism and user type.
The statistical information begins with the month when the first logon request is registered, and continues to the
current month.
Note
If you need statistics for the period before August 2015 you can create an Incident on SAP Support Portal
with a component BC-IAM-IDS.
Currently the statistics does not include the logon requests when Identity Authentication acts as a proxy to
delegate authentication to an external corporate identity provider.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
The Security Assertion Markup Language (SAML) version 2.0 is a standard for the communication of assertions
about principals, typically users. The assertion can include the means by which a subject was authenticated,
attributes associated with the subject, and an authorization decision for a given resource.
Related Information
SAML Specifications
This section is intended to help administrators deal with error messages in the administration console for SAP
Cloud Platform Identity Authentication service.
Table 45:
Error Message Description Solution
This field is required This field is empty. You must enter at least one non-space
character.
Internal error; contact system adminis Unexpected error occurred. ● Try again.
trator ● Check the browser logs.
● Contact an operator of Identity
Authentication.
The provided file is of wrong type; spec You have specified a wrong file format. You should use the following files:
ify a different file
● For service provider metadata, use
XML.
● For privacy policy and terms of use
documents, use plain text files.
● For certificate for API authentica
tion, use base64-encoded certifi
cate.
The imported CSV file contains entries You have provided a CSV file with a mail Correct the file so that the mail column
with a duplicate email <email address>. column that has the same email entries. contains unique values.
The values under mail column must be
unique.
The imported CSV file contains entries You have provided a CSV file with a Correct the file so that the loginName
with a duplicate login name <login loginName column that has the same en column contains unique values.
name>. The values under loginName col tries.
umn must be unique.
First <number> users are imported. The first <number> users in the CSV file Delete the first <number> users from
are already imported for the tenant. The the CSV file, correct the invalid row, and
User import has been interrupted due to
next user was not imported because the re-import the updated file.
an invalid entity. CSV file contains an incorrect data for
that user.
...
First <number> users are imported. The first <number> users in the CSV file ● Correct the user data, delete the
are already imported for the tenant. The first <number> users from the CSV
User import has been interrupted due to
next user was not imported because its file, and re-import the updated file.
multiple users in the database with the email matches with the email of other ● Contact an operator of Identity
same email address <email address>. users. Authentication to check if your
The email address must be unique for emails exist in the database.
each user.
First <number> users are imported. The first <number> users in the CSV file ● Correct the email for the login name
are already imported for the tenant. The under the mail column, delete the
User import has been interrupted for
next user was not imported because its first <number> users from the CSV
user with email address <email ad data in the CSV file conflicts with the file, and re-import the updated file.
dress>. data in the database.
... Caution
During CSV import, you cannot
change the email of an existing
user.
Note
You cannot have two users with
the same login name, but with
different emails.
Your e-mail activation link is invalid. The link that the user has followed has
● The user should visit the
expired or has already been used.
application choose Log On
follow Forgot Password link . This
will trigger the Forgot Password
process and the user will receive an
e-mail to reset his or her password.
● Delete the user and create it again.
● Valid for the User Import scenario.
If the user was imported via a CSV
file, check if you have sent the acti
vation e-mails. For more informa
tion, see Import or Update Users for
a Specific Application [page 68].
Related Information
This user guide describes the scenarios in the SAP Cloud Platform Identity Authentication service from a user’s
perspective. It is aimed at consumers, partners, and employees.
For the scenarios, users can use services to maintain or update their user profiles and to log on to applications.
User services are divided into profile and sign-on services. For configuration of certain profile services, users
access the profile page at https://<tenant ID>.accounts.ondemand.com/.
● Basic authentication
Users can log on to applications by providing basic credentials, such as user name and password.
● Single Sign-On authentication
Users can access cloud applications via SAML 2.0 based single sign-on.
● Two-Factor authentication
If the application requires two-factor authentication, users should provide a passcode generated by a mobile
device as an addition to the basic authentication. For more information, see Two-Factor Authentication [page
184].
● Self-registration
If this option is activated by an administrator, a user can register when he or she accesses the application’s
logon page. When the user clicks on the Register Now link, a registration form appears, where he or she needs
Note
If the user has not received the activation e-mail, he or she can do the following:
○ Check the Deleted, Junk or other folders in his or her mail box.
○ Follow the Forgot Password link in the logon page of the application. If the registration was successful,
this will trigger the Forgot Password process, and the user will receive an e-mail with instructions how
to reset the password.
○ Choose the Register Now link, and fill in the registration form again.
○ Contact the system administrator of the application.
○ Forgot password
A user can change his or her password when he or she accesses the application’s logon page. When
the user clicks on the Forgot Password link, the user triggers the forgot password process.
● Social sign-on
If this feature is enabled by an administrator, users can link their Identity Authentication accounts with social
network accounts. That way they can authenticate through a social provider by choosing the social network
button on the logon page. They can also unlink their accounts on the profile page.
Tip
Users can access the profile page at https://<tenant ID>.accounts.ondemand.com/.
Note
The E-mail and Login Name fields cannot be edited on the profile page. These fields can be edited by the
tenant administrator via the administration console for Identity Authentication.
Note
Users must familiarize themselves with the password policy for logging on to the respective application. If
no password policy is set for the application, users are able to modify their passwords with any characters
of their choosing.
Related Information
This document provides information about activation and deactivation, performed on the user profile page, of a
mobile device to generate passcodes for two-factor authentication.
With two-factor authentication, you are required to provide a one-time password (OTP), also called a passcode, in
addition to your primary credentials. Passcodes are time-based and are valid for one login attempt only, thus
providing additional security to the common static passwords. Passcodes are generated by an authenticator
application. The authenticator is a mobile application that you install on your mobile devices. The configurations in
this guide are for the SAP Authenticator application. You can also use other third-party authenticators such as
Google Authenticator or Microsoft Authenticator. For more information about how to install and configure
authenticators other than SAP Authenticator see their documentation.
Related Information
To log on to applications that require two-factor authentication, you have to activate a mobile device that will
generate passcodes.
Prerequisites
● You have installed a QR code scanner and an SAP Authenticator application on your mobile device.
Note
You can also use other third-party authenticators such as Google Authenticator or Microsoft
Authenticator. For more information about how to install and configure authenticators other than SAP
Authenticatior see their documentation.
Note
SAP Authenticator runs on both iOS and Android mobile operating systems.
Context
Some applications require two-factor authentication as an additional security to the common static passwords.
They will ask you to provide your password and a passcode, generated by a mobile device.
Note
Passcodes are only necessary for applications that require two-factor authentication. You do not need to
activate a device for applications that only require passwords for authentication.
Procedure
Results
Now you can log on to applications that require passcode as an additional security for authentication.
Related Information
This document shows you how to deactivate your mobile devices that you use to generate passcodes for access
to applications requiring two-factor authentication.
Context
You can deactivate the mobile devices with authenticator if you do not want to use them any more to generate
passcodes.
Note
If you deactivate your mobile devices, you will not be able to log on to applications that require passcodes any
more. To be able to access the applications again, you have to activate again a device on the user profile page.
For more information, see the Related Information.
If your mobile device has been lost or stolen, or you cannot provide a valid passcode, contact your system
administrator.
Procedure
Related Information
You can log on to applications that use SAP Cloud Platform Identity Authentication service via your accounts in
Twitter, Facebook, LinkedIn, or Google.
Prerequisites
Context
Using the social network authentication, you link your Identity Authentication account with your social network
account or accounts. After the initial setup, when you link the accounts, you can log on to the applications with
your social network credentials.
Identity Authentication has access to the following data from the social providers:
Table 46:
Social Identity Provider Data Used by SAP Cloud Platform Identity Authentication
Service
This data is used for the initial linking of your Identity Authentication account with the social network account.
Later, if you update the personal information in your social account, the updated information will not be copied by
Identity Authentication.
To link your Identity Authentication account with a social network account, proceed as follows:
Procedure
Note
Which social networks are displayed on the page depends on the application.
○ Link your Identity Authentication account with your social network account.
○ Create a new Identity Authentication account that will be linked with your social network account.
Note
This option appears only for applications that allow user registration.
Once you allow Identity Authentication to link your account with the social providers' accounts, you can log on to
the applications via the social providers.
You can unlink your social provider account via the profile page.
Context
To remove your social network logon information from your Identity Authentication account, proceed as follows:
Procedure
If the operation is successful, the system displays the message Profile updated .
With the Remember me functionality enabled, you can log on to an application without the need to provide your
credentials every time you access it.
Context
If you enable the Remember me functionality, the application saves a cookie in the browser and automatically logs
you on next time you access the application. Once enabled, the Remember me functionality is valid for 3 months
unless you log out from the application.
Note
If the application requires two-factor authentication, you must provide a valid one-time password (passcode)
generated by a mobile device every time you access the application. For more details about how to use two-
factor authentication on your mobile device, see Related Information.
1. Access the application that you want to log on to with Remember me.
2. Provide your credentials and select the Remember me check box.
3. Optional: Provide a passcode if required.
Results
Next time you access the application, you will be logged on automatically. If the application requires two-factor
authentication, you need to provide a valid passcode, generated by a mobile device.
Note
If you want to disable Remember me for an application log out from the application, and do not select the
checkbox next time you log on.
Related Information
You can access trusted applications that require two-factor authentication via your mobile devices using single
sign-on (SSO).
Prerequisites
This feature allows you to access applications via your mobile device without the need to type manually your
username, password and passcode. The first time you access the application, you will be prompted to provide
your credentials. If you have enabled the Remember me functionality, you will be logged on next time on the basis
of the cookie saved in the browser. For more details anout the Remember me functionality, see Related
Information.
Procedure
To add the application, you need to scan a QR code or type the application's link manually. Your administrator
should provide you with the QR code or the application's link. The link follows the following pattern:
https://<tenant_ID>.accounts.ondemand.com/saml2/idp/sso?
sp=<sp_name>[&RelayState=<sp_specific_value>&index=<index_number>]&j_username=[user
name]&j_otpcode=[passcode]
3. Log on to the application via SAP Authenticator.
4. Select the Remember me check box.
5. Provide your credentials.
Results
You are now logged on to the application. Next time you try to log on to this application via SAP Authenticator, you
will not have to provide your credentials and a passcode. The system will log you on automatically.
Related Information
You can change your current password via your profile page.
Context
Your password grants you access to any platform connected to SAP Cloud Platform Identity Authentication
service. You can change your password by triggering the change password process. To change your current
password you need to provide the current and the new passwords to the system. You also must comply with the
password requirements.
Tip
If you don't know your current password, follow the Forgot Password link in the logon page of the application.
This will trigger the Forgot Password process, and you will receive an e-mail with instructions how to reset your
password.
Procedure
Results
Remember
Your password can only be changed once every 24 hours.
This section aims to help end users to deal with error messages when using applications for logon, registration,
invitation, password update, and account activation.
Error Codes
Authentication failed; try again ● You have entered the wrong cre ● Try again;
dentials; ● Open your e-mail and activate your
● Your account is not activated. account;
● Register on the logon page;
● Contact your administrator.
Account is locked; select the link in the You are not allowed to log on to your ac ● Check the e-mail you received from
e-mail that has been sent to unlock your count. SAP Cloud Platform Identity
account; Authentication service with instruc
tions about how to unlock your ac
count;
● Contact your administrator.
Insufficient password complexity; check Your password does not comply with the Familiarize yourself with the password
password requirements application’s password policy. policy for the application.
Cannot verify your password; try again The old password for the password up Enter your correct current password.
date is invalid.
The password has already been changed According to the application’s policy, ● Familiarize yourself with the appli
in the last 24 hours you are not allowed to change the pass cation's policy for changing the
word right now. password;
● Try again later.
Your e-mail activation link is invalid. The e-mail activation link that you have
● Visit the application choose
received is expired or already used by
you. Log On follow Forgot Password
link
● Contact your administrator.
Related Information
The developer guide is aimed mainly at organization developers who can implement configurations in addition to
the ones in the administration console of SAP Cloud Platform Identity Authentication service.Developers can use
REST API services to configure various authentication and registration mechanisms for their applications. The
applications that administrators configure use different application services for all user-related processes.
Application Services
The application services are used by the cloud services and cloud applications to interact with Identity
Authentication with regard to user records in the tenant.
Related Information
Developers can choose the type of authentication when API methods of SAP Cloud Platform Identity
Authentication service are used.
For more information about the API methods, see Invitation REST API [page 198] and User Management REST
API [page 200].
The certificate to be used for authentication by the REST APIs of Identity Authentication must be requested from
the SAP Support Portal .
Context
You can use a user ID and a password to authenticate when REST API calls to the tenant of Identity Authentication
are used. The system automatically generates a user ID when the password is set for the first time.
Note
The password must meet the following conditions:
The password is locked for 60 min after 5 failed logon attempts with wrong value.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
Type the name of the application in the search field to filter the list items, or choose the application from
the list on the left.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Note
If you are setting the password for API authentication for the first time, these fields are empty.
Once the password has been saved, the system displays a message informing you of this.
This document describes how developers configure the certificate used for authentication when API methods of
SAP Cloud Platform Identity Authentication service are used.
Prerequisites
You have requested a client certificate from the SAP Support Portal .
Context
For the configuration, you have to provide the base64-encoded certificate as a file or plain text.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
If you do not have a created application in your list, you can create one. For more information, see Create a
New Application [page 29].
Note
For the upload, you have to use .cer or .crt files.
Once the certificate has been uploaded, the system displays the message Certificate for API
authentication updated.
Related Information
This document contains references to the API Documentation of SAP Cloud Platform Identity Authentication
service.
REST APIs
The invitation service allows you to implement a request for user invitations. The invitees then receive an e-mail
containing information about how to register.
Prerequisites
● You need to set up the authentication type to access the API. For more information about this configuration,
see API Authentication [page 48]
Resources
To configure the invitation service, you use a POST request with the following URI: https://<tenant
ID>.accounts.ondemand.com/cps/invite/.
Representation
You have to use a JSON representation of the invitation request by specifying application/json content type. All
declared parameters in the request must also be JSON encoded.
Parameters
Note
Only inviteeEmail or inviteeUserId should be
used, not both.
Note
Only inviteeEmail or inviteeUserId should be
used, not both.
inviterName The display name of the user who sends the invitation.
Note
The targetUrl parameter is optional if a Home URL is
set for the application, and the application does not use
overlay.
sourceUrl The URL for the invitation link in the e-mail sent to the invitee.
Note
The sourceUrl parameter is optional if a Home URL is
set for the application, and the application does not use
overlay.
Example
POST /cps/invite/
Content-Type: application/json
{
"inviteeEmail": "[email protected]",
"inviteeFirstName": "John",
"inviteeLastName": "Miller",
"inviterName": "Donna Moore",
"footerText": "Invitation footer sample text",
"headerText": "Invitation header sample text",
"targetUrl": "http://www.myserviceprovider.com/home_page/",
"sourceUrl": "http://www.myserviceprovider.com/home_page/"
}
This REST API allows you to implement a request for a user registration and a request for verification of a user
password or certificate. You thus allow administrators to register business partners on their behalf or to check
user credentials.
The user registration service is used for registration of new users or for on-behalf registration of partners.
Prerequisites
● You need to set up the authentication type to access the API. For more information about this configuration,
see API Authentication [page 48]
Resource
For this service, you need to use the following URI: https://<tenant ID>.accounts.ondemand.com/
service/users
Representation
You have to specify application/x-www-form-urlencoded content type. All declared parameters in the request
must be URL-encoded.
Parameters
first_name The first name of the user you register. The allowed maximum
length for the first name is 32 characters.
last_name The last name of the user you register. The allowed maximum
length for the last name is 64 characters.
source_url The URL to the public page of the application where the SAP
Cloud Platform Identity Authentication service overlays are in
tegrated. If not provided, the activation screen is shown with
out overlays. This parameter value must be URL-encoded.
target_url The URL to the application page that the user should be redir
ected to after he or she has completed account activation. If
target_url is not provided, the user is redirected to the
home URL configured for the service provider.
Note
If the user is new, the activation link is returned with
the 201 response.
spCustomAttribute4
spCustomAttribute5
POST Request
Example
POST Request
Caution
All parameters for the POST method must be written on one line.
POST /service/users
Content-Type: application/x-www-form-urlencoded
name_id=johns&user_profile_id=p987654&[email protected]&first_name=John&las
t_name=Smith&language=en&valid_from=20110901120000Z&valid_to=20120901110000Z&sourc
e_url=https%3A%2F%2Ffanyv88.com%3A443%2Fhttp%2Fwww.myapp.com%2Fpublic.jsp&target_url=http%3A%2F
%2Fwww.myapp.com%2Fprotected.jsp&spCustomAttribute1=Industry
POST Response
Example
The URI of the created user is returned in the location header of the HTTP Response.
Example
In case of conflict, the URI of the conflicting user is returned in the location header of the HTTP Response.
Example
In case of creating a new user with "send_email=false", the activation link is returned in the HTTP Response
body.
Content-Type: application/json
{
"activationLink" : "https://<tenant ID>.accounts.ondemand.com/ids/
activation?
token=I1830C497BF9B857B7D6298E5F117AF397I1F59A28838A3276E8B68FFFF54414C8843ACF395A
05401ABE6568FF3659D6EE96"
name_id The name ID of the SP user that you retrieve the URI for.
GET Request
Example
GET Request
GET /service/users?name_id=johns&sp_name=jpaas.developer
GET Response
The URI of the created user is in the location header of the HTTP Response.
Example
Related Information
This section contains information about the SAP Cloud Platform Identity Authentication service implementation
of the System for Cross-domain Identity Management (SCIM) REST API protocol.
Prerequisites
To call the methods of this SCIM REST API you must have a system as administrator with an assigned Manage
Users role. For more details about how to add a system as administrator and assign administrator roles, see Add
System as Administrator [page 144], and Edit Administrator Authorizations [page 146].
Note
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with an URL in it. This URL contains the tenant ID.
Some of the attributes have predefined supported values. They are returned as a map of key value pairs. See
some examples in the table below. For the full set of attributes, copy the URL from the table, replace <tenant
ID> with your Tenant ID, and open the edited URL in a web browser.
Note
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with an URL in it. This URL contains the tenant ID.
Table 53:
Related Information
The user search method of the SAP Cloud Platform Identity Authentication service implementation of the SCIM
REST API protocol allows you to perform a request for user search. User search is implemented as defined by the
System for Cross-domain Identity Management (SCIM) protocol for querying and filtering resources.
Content-Type: application/scim+json
Authentication mechanisms:
● Client certificate
● Basic authentication
Request Parameters
Table 54:
Parameter Required Description
filter No Defines the search criteria. If missing, the search criteria will depend on the
other parameters.
count No Paginates the response. Represents the number of items which will be re
turned per page.
Note
If you have more than 100 user, and you want to get the full list, you
have to perform multiple requests.
startIndex No Paginates the response. Represents the start index from which the results
are returned.
Note
If none of the request parameters are included, the number of items which will be returned per page will be at
most 100 starting from index 1.
Supported Operators
Table 55:
Attribute Description
addresses.country The [home]country of the user. The value is in the ISO 3166-1
alpha 2 "short" code format. [ISO3166 ].
Request Example
Example
Response
Format: JSON
The response contains a list of users with the following user attributes:
● meta
● userType
● name_id
● id
● emails.value
● name.honorificPrefix
● name.givenName
● name.familyName
● userName
● addresses[work].streetAddress
● addresses[work].locality
Note
The attribute equals to city.
● addresses[work].region
● addresses[work].postalCode
● addresses[work].country
● addresses[home].streetAddress
● addresses[home].locality
Note
The attribute equals to city.
● addresses[home].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[home].postalCode
● addresses[home].country
● locale
● phoneNumbers[work].value
● phoneNumbers[mobile].value
● phoneNumbers[fax].value
● timezone
● active
Note
If the active parameter and its value are not present in the response, the user status is equivalent to the
new status in Identity Authentication.
● displayName
● contactPreferenceEmail
● contactPreferenceTelephone
● industryCrm
● company
● companyRelationship
● department
● groups
● corporateGroups
Note
This attribute is applicable for the corporate user store scenarios and contains the groups the user in the
corporate user store is assigned to.
Note
Supported values: initial, enabled, and disabled.
● userType
Note
Supported values: public, partner, customer, and employee.
Note
The values of the following attributes are returned when the Enterprise User Schema Extension is used.
● employeeNumber
● costCenter
● organization
Note
Equals the company attribute from the Core schema.
● division
● department
Note
Equals the department attribute from the Core schema.
● manager
○ value
○ $ref
○ displayName
Note
Read only.
Administrators at Identity Authentication can store, read, create and update customer specific data in up to 10
custom attributes via the SCIM API.
Note
The values of the following attributes are returned when the Custom Attributes Schema Extension
(urn:sap:cloud:scim:schemas:extension:custom:2.0:User) is used.
Note
name can take values from customAttribute1 to customAttribute10.
○ value
Note
value must be a string with a maximum length of 256 characters.
The response does not contain the whole User resource object. It returns only the specified attributes here, as if
you have limited the response to those attributes using the attributes query parameter. totalResults shows
the total number of results matching the query.
For more information about the general error codes that may be returned, see General Error Codes [page 247].
Response Example
Example
{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:ListResponse"],
"totalResults": 1,
"itemsPerPage": 10,
"startIndex": 1,
"Resources": [{
"userName": "johnsmith",
"meta": {
"location": "https://<tenant ID>.accounts.ondemand.com/service/scim/
Users/P000000",
"resourceType": "User",
"version": "1.0",
"created": "2013-06-18T13:05:51Z",
"lastModified": "2015-08-21T11:19:50Z"
},
"name": {
"givenName": "John",
"familyName": "Smith",
"honorificPrefix": "Mr."
},
"emails": [{
"value": "[email protected]"
}],
"addresses": [{
"type": "work",
"division" : "Finance",
"department" : "Administration",
"manager" : {
"value" : "P999913",
"$ref" : "https://<tenant ID>.accounts.ondemand.com/service/scim/
Users/P999913",
"displayName" : "Jane Watson"
}
},
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User":
{
"attributes":
[
{
"name": "customAttribute1",
"value": "Home Address2"
},
The user resource method of the SAP Cloud Platform Identity Authentication service implementation of the SCIM
REST API protocol provides information on a known user.
Note
User resource is implemented as defined by the SCIM protocol.
Request
Content-Type: application/scim+json
Authentication mechanisms:
● Client certificate
● Basic authentication
Request Parameters
Table 58:
Parameter Required Description
Request Example
Example
GET /service/scim/Users/P000000
Format: application/scim+json
Response
The response contains user object with the following user attributes:
● meta
● userType
● name_id
● id
● emails.value
● name.honorificPrefix
● name.givenName
● name.familyName
● userName
● addresses[work].streetAddress
● addresses[work].locality
Note
The attribute equals to city.
● addresses[work].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[work].postalCode
● addresses[work].country
● addresses[home].streetAddress
● addresses[home].locality
Note
The attribute equals to city.
● addresses[home].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[home].postalCode
● addresses[home].country
● locale
Note
If the active parameter and its value are not present in the response, the user status is equivalent to the
new status in Identity Authentication.
● displayName
● contactPreferenceEmail
● contactPreferenceTelephone
● industryCrm
● company
● companyRelationship
● department
● groups
● corporateGroups
Note
This attribute is applicable for the corporate user store scenarios and contains the groups the user in the
corporate user store is assigned to.
● passwordStatus
Note
Supported values: initial, enabled, and disabled.
● userType
Note
Supported values: public, partner, customer, and employee.
● socialIdentities
Note
Returns information about the social accounts that are linked to the user's account in Identity
Authentication. Supported values: socialId, socialProvider, and dateOfLinking.
Note
The values of the following attributes are returned when the Enterprise User Schema Extension is used.
Note
Equals the company attribute from the Core schema.
● division
● department
Note
Equals the department attribute from the Core schema.
● manager
○ value
○ $ref
○ displayName
Note
Read only.
Administrators at Identity Authentication can store, read, create and update customer specific data in up to 10
custom attributes via the SCIM API.
Note
The values of the following attributes are returned when the Custom Attributes Schema Extension
(urn:sap:cloud:scim:schemas:extension:custom:2.0:User) is used.
● attributes
○ name
Note
name can take values from customAttribute1 to customAttribute10.
○ value
Note
value must be string with a maximum length of 256 characters.
Example
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User"],
"userName": "johnsmith",
"meta": {
"location": "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P000000",
"resourceType": "User",
"version": "1.0",
"created": "2013-06-18T13:05:51Z",
"lastModified": "2015-08-21T11:19:50Z"
},
"name": {
"givenName": "John",
"familyName": "Smith",
"honorificPrefix": "Mr."
},
"emails": [{
"value": "[email protected]"
}],
"addresses": [{
"type": "work",
"streetAddress": "100 Universal City Plaza",
"locality": "Hollywood",
"region": "CA",
"postalCode": "91608",
"country": "US"
}, {
"type": "home",
"streetAddress": "456 Hollywood Blvd",
"locality": "Hollywood",
"region": "CA",
"postalCode": "91608",
"country": "US"
}],
"phoneNumbers": [{
"value": "555-555-5555",
"type": "work"
}, {
"value": "555-555-4444",
"type": "mobile"
}, {
"value": "555-555-4444",
"type": "fax"
}],
"locale": "DE",
"timezone": "Europe/Berlin",
"userType": "partner",
"active": true,
"groups": [{
"value": "admin",
"$ref": "https://<tenant ID>.accounts.ondemand.com/service/groups/
55b87ab4e4b0fc7a00bbc070",
"display": "Administrators"
}],
"displayName": "JohnSmith",
"contactPreferenceEmail": "yes",
"contactPreferenceTelephone": "no",
"industryCrm": "Consumer Products",
"companyRelationship": "Partner",
"passwordStatus": "disabled",
"corporateGroups": [
{
"value": "admin"
}
],
"socialIdentities": [{
"socialId": "3375377405",
"socialProvider": "Twitter",
"dateOfLinking": "20160420064555Z"
}, {
"socialId": "138244449858760",
"socialProvider": "Facebook",
"dateOfLinking": "20160419143031Z"
}, {
"socialId": "GLhp_za6Hq",
"socialProvider": "LinkedIn",
"dateOfLinking": "20160420064732Z"
},
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" : {
"employeeNumber" : "JohnS",
"costCenter" : "costCenter",
"organization" : "SFSF",
"division" : "Finance",
"department" : "Administration",
"manager" : {
"value" : "P999913",
}
},
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User":
{
"attributes":
[
{
"name": "customAttribute1",
"value": "Home Address2"
},
{
"name": "customAttribute2",
"value": "Telephone2"
}
]
}
}
The create user resource method of the SAP Cloud Platform Identity Authentication service implementation of
the SCIM REST API protocol provides information on the creation of a user.
Note
Create user resource is implemented as defined by the SCIM protocol.
Request
Content-Type: application/scim+json
Authentication mechanisms:
● Client certificate
● Basic authentication
Supported Attributes
● emails.value
Note
Only one value is supported.
● sendMail
Note
The parameter supports boolean values true and false. The default value is true. If you do not want to
send an e-mail, the value should be passed with value false.
● mailVerified
Note
The parameter supports boolean values true and false. The default value is false.
● name.honorificPrefix
● name.givenName
● name.familyName
● userName
● addresses[work].streetAddress
● addresses[work].locality
Note
The attribute equals to city.
● addresses[work].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[work].postalCode
● addresses[work].country
● addresses[home].streetAddress
● addresses[home].locality
Note
The attribute equals to city.
● addresses[home].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[home].postalCode
● addresses[home].country
● locale
● password
Note
If the attribute password is provided, user is prompted to change the password on first login.
passwordStatus will be initial as a default value.
● passwordStatus
● phoneNumbers[work].value
● phoneNumbers[mobile].value
● phoneNumbers[fax].value
● timezone
● active
Note
The parameter supports only boolean values true and false. They are equivalent to the active and
inactive status in Identity Authentication.
If the active parameter is not present in the request the user is created with a status new.
● displayName
● contactPreferenceEmail
● contactPreferenceTelephone
● industryCrm
● company
● companyRelationship
Note
If the userType attribute is provided and has one of the values Customer, Employee, or Partner, the
companyRelationship attribute value is overwritten and takes the same value as the userType
attribute.
● department
● groups
Note
It is possible to assign companyGroups to a user only if the groups are already existing.
● corporateGroups
Note
This attribute is applicable for the corporate user store scenarios and contains the groups the user in the
corporate user store is assigned to.
● sourceSystem
● userType
Note
Supported values: public, partner, customer, and employee.
Note
The values of the following attributes are returned when the Enterprise User Schema Extension is used.
● employeeNumber
● costCenter
● organization
Note
Equals the company attribute.
● division
● department
Note
Equals the department attribute from the Core schema.
● manager
○ value
Note
The id of the user's manager.
○ $ref
Note
The resource URL of the manager.
○ displayName
Note
Read only.
Administrators at Identity Authentication can store, read, create and update customer specific data in up to 10
custom attributes via the SCIM API.
Note
The values of the following attributes are returned when the Custom Attributes Schema Extension
(urn:sap:cloud:scim:schemas:extension:custom:2.0:User) is used.
● attributes
○ name
○ value
Note
value must be a string with a maximum length of 256 characters.
The following scenarios are possible via the SCIM REST API:
Table 60:
Result A new user will be created. Create a user that is provi Create a user that comes
sioned from another system. from the corporate user
The user will be able to log on. store. The user will be able to
He or she will receive e-mail, log on to the application di
but does not have to click a rectly.
verification link in the e-mail.
Request Example
Example
"userName": "johnsmith",
"name": {
"givenName": "John",
"familyName": "Smith",
"honorificPrefix": "Mr."
},
"emails": [{
"value": "[email protected]"
}],
"addresses": [{
"type": "work",
"streetAddress": "100 Universal City Plaza",
"locality": "Hollywood",
"region": "CA",
"mailVerified": "true",
"corporateGroups": [
{
"value": "admin"
}
],
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" : {
"employeeNumber" : "JohnS",
"costCenter" : "costCenter",
"organization" : "SFSF",
"division" : "Finance",
"department" : "Administration",
"manager" : {
"value" : "P999913",
"$ref" : "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P999913"
}
},
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User":{
"attributes":[{
"name":"customAttribute1",
"value":"Home Address2"
},
{
"name":"customAttribute2",
"value":"Telephone2"
}
Response
Format: application/scim+json
Note
Response code is 400 Bad Request if user with id provided in the value attribute of the manager attribute
from the enterprise schema does not exist.
The URI of the newly created user is in the location header of the HTTP Response.
Response Example
Example
Body:
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User"],
"userName": "johnsmith",
"id": "P057607",
"meta": {
"location": "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P000000",
"resourceType": "User",
"version": "1.0",
"created": "2013-06-18T13:05:51Z",
"lastModified": "2015-08-21T11:19:50Z"
},
"name": {
"givenName": "John",
"familyName": "Smith",
"honorificPrefix": "Mr."
},
"emails": [{
"value": "[email protected]"
"mailVerified": "true",
"corporateGroups": [
{
"value": "admin"
}
],
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" : {
"employeeNumber" : "JohnS",
"costCenter" : "costCenter",
"organization" : "SFSF",
"division" : "Finance",
"department" : "Administration",
"manager" : {
"value" : "P999913",
"$ref" : "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P999913",
"displayName" : "Jane Watson"
}
},
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User" : {
"attributes" : [ {
"name" : "customAttribute1",
"value" : "Home Address2"
}, {
The update user method of the SAP Cloud Platform Identity Authentication service implementation of the SCIM
REST API protocol provides information on the update of a known user. The method does not create a new user.
Note
Update is provided only on the attributes with new values. The other attributes remain the same.
Request
Content-Type: application/scim+json
Authentication mechanisms:
● Client certificate
● Basic authentication
Supported Attributes
Attributes are case sensitive and only the exact case should be used.
● id
Note
Attribute id is required in the request json and must match the path parameter id.
● emails.value
Note
Only one value is supported.
● name.honorificPrefix
● name.givenName
● name.familyName
● userName
● addresses[work].streetAddress
Note
The attribute equals to city.
● addresses[work].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[work].postalCode
● addresses[work].country
● addresses[home].streetAddress
● addresses[home].locality
Note
The attribute equals to city.
● addresses[home].region
Note
The attribute is relevant only for Canada and the United States of America. It equals to the state in these
countries.
● addresses[home].postalCode
● addresses[home].country
● locale
● phoneNumbers[work].value
● phoneNumbers[mobile].value
● phoneNumbers[fax].value
● timezone
● active
Note
If the active parameter and its value are not present in the request, this means that the user status
remains unchanged.
● displayName
● contactPreferenceEmail
● contactPreferenceTelephone
● industryCrm
● company
● companyRelationship
● department
● groups
Note
It is possible to assign companyGroups to a user only if the groups are already existing.
● corporateGroups
Note
This attribute is applicable for the corporate user store scenarios and contains the groups the user in the
corporate user store is assigned to. The following options are possible:
○ If the attribute corporateGroups is provided with a specific value, this value will overwrite the previous
one.
○ If the attribute corporateGroups is not provided, this previous value of the attribute will be preserved.
○ If the attribute corporateGroups is provided without a value, the previous value will be deleted.
● password
Note
If attribute password is provided the password will be changed.
● passwordStatus
Note
If the password attribute is provided the passwordStatus can be set to enabled or initial. When this
attribute is provided the password attribute is a required parameter.
● userType
Note
Supported values: public, partner, customer, and employee.
● sendMail
Note
The parameter supports boolean values true and false. The default value is true. If you do not want to
send an e-mail, the value should be passed with value false.
● mailVerified
Result The user will receive e- The user will receive e- The user will be able to The user will not be
mail. He or she will be mail. He or she has to log on to the applica able to log on.
able to log on. click the verification tion directly.
link in the e-mail.
Note
The values of the following attributes are returned when the Enterprise User Schema Extension is used.
● employeeNumber
● costCenter
● organization
Note
Equals the company attribute from the Core schema.
● division
● department
Note
Equals the department attribute from the Core schema.
● manager
○ value
○ $ref
○ displayName
Note
Read only.
Administrators at Identity Authentication can store, read, create and update customer specific data in up to 10
custom attributes via the SCIM API.
● attributes
○ name
Note
name can take values from customAttribute1 to customAttribute10.
○ value
Note
value must be string with a maximum length of 256 characters.
If you provide empty value, it will delete the attribute if it already exists.
If you provide an empty list of attributes, the custom attributes that are already set will be deleted.
Request Example
Example
{
"userName": "johnsmith",
"id": "P000000",
"name": {
"givenName": "John",
"familyName": "Smith",
"honorificPrefix": "Mr."
},
"emails": [{
"value": "[email protected]"
}],
"addresses": [{
"type": "work",
"streetAddress": "100 Universal City Plaza",
"locality": "Hollywood",
"region": "CA",
"postalCode": "91608",
"country": "US"
}, {
"type": "home",
"streetAddress": "456 Hollywood Blvd",
"locality": "Hollywood",
"region": "CA",
"postalCode": "91608",
"country": "US"
}],
"phoneNumbers": [{
"value": "555-555-5555",
"type": "work"
}, {
"passwordStatus": "enabled",
"sendMail":"false",
"mailVerified": "true",
"corporateGroups": [
{
"value": "admin"
}
],
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" : {
"employeeNumber" : "JohnS",
"costCenter" : "costCenter",
"organization" : "SFSF",
"division" : "Finance",
"department" : "Administration",
"manager" : {
"value" : "P999913",
"$ref" : "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P999913"
}
},
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User":{
"attributes":[{
"name":"customAttribute1",
"value":"Home Address2"
},
{
"name":"customAttribute2",
"value":"Telephone2"
}
]}
Response
Format: application/scim+json
Note
Response code is 400 Bad Request if user with id provided in the value attribute of the manager attribute
from the enterprise schema does not exist.
For more information about the general error codes that may be returned, see General Error Codes [page 247].
Response Example
Example
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User"],
"userName": "johnsmith",
"meta": {
"location": "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P000000",
"resourceType": "User",
"version": "1.0",
"created": "2013-06-18T13:05:51Z",
"lastModified": "2015-08-21T11:19:50Z"
},
"id": "P000000",
"name": {
"givenName": "John",
"familyName": "Smith",
"honorificPrefix": "Mr."
},
"addresses": [{
"type": "work",
"streetAddress": "100 Universal City Plaza",
"locality": "Hollywood",
"region": "CA",
"postalCode": "91608",
"country": "US"
}, {
"type": "home",
"streetAddress": "456 Hollywood Blvd",
"locality": "Hollywood",
"region": "CA",
"postalCode": "91608",
"country": "US"
}],
"phoneNumbers": [{
"value": "555-555-5555",
"type": "work"
}, {
"value": "555-555-4444",
"mailVerified": "true",
"corporateGroups": [
{
"value": "admin"
}
],
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" : {
"employeeNumber" : "JohnS",
"costCenter" : "costCenter",
"organization" : "SFSF",
"division" : "Finance",
"department" : "Administration",
"manager" : {
"value" : "P999913",
"$ref" : "https://<tenant ID>.accounts.ondemand.com/service/scim/Users/
P999913",
"displayName" : "Jane Watson"
}
},
"urn:sap:cloud:scim:schemas:extension:custom:2.0:User":
{
"attributes":
[
{
"name": "customAttribute1",
"value": "Home Address2"
},
{
"name": "customAttribute2",
"value": "Telephone2"
}
]
}
}
The delete user resource method of the SAP Cloud Platform Identity Authentication service implementation of the
SCIM REST API protocol allows you to delete an existing user. Delete user resource is implemented as defined by
the System for Cross-domain Identity Management (SCIM) protocol.
Request
Content-Type: application/scim+json
Authentication mechanisms:
● Client certificate
● Basic authentication
Note
Response code if user does not exist is 404 Not Found. When user resource is deleted, it is not possible to get
information about it via a GET request.
For more information about the general error codes that may be returned, see General Error Codes [page 247].
Related Information
The Change Tenant Texts REST API of SAP Cloud Platform Identity Authentication service can be used to change
the predefined texts and messages for end-user screens available per tenant in the Identity Authentication.
Prerequisites
To call the methods of this Change Tenant Texts REST API you must have a system as administrator with an
assigned Manage Tenant Configuration role. For more details about how to add a system as administrator and
assign administrator roles, see Add System as Administrator [page 144], and Edit Administrator Authorizations
[page 146].
Usage
The predefined tenant texts are stored in the tenant_texts.properties file which can be downloaded from:
Tenant Texts. The file contains configurable parameters stored as key value pairs of strings. Each key stores the
name of a parameter, and the corresponding value is the text that can be changed and updated. The keys are self-
explanatory and show where the texts are used. For example, the logon.ui.label.user=E-mail key value pair
is for the type of information that the user needs to provide in order to log on to the application. In this case, this is
the E-Mail.
Methods
Table 65:
HTTP Method See URI
Note
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with an URL in it. This URL contains the tenant ID.
Download the texts that overwrote part of the predefined tenant texts when your custom tenant was created.
Request
Content-Type: application/json
URL Parameters
Table 66:
Parameter Required Description Notes
setId No The identifier of the scenario that the re The default value is
source is related to. SAP_DEFAULT
locale Yes The locale of the resource. The default languages are:
● English (en)
● French (fr)
● German (de)
● Chinese (zh)
● Portuguese (pt)
● Spanish (es)
Request Example
GET /service/resource?resourceType=RESOURCE_I18N_BUNDLE&locale=en
Response
415 Unsupported Media Type The REST service does not support the
API version requested by the REST cli
ent.
Response Example
Caution
Make sure that you have removed the comment lines and applied the proper escaping in your POST request.
The comment lines are introduced by the # (number or hash) sign.
You should add \n at the end of each line in the data property content.
\n New line
\r Carriage return
\t Tab
\\ Backslash character
Tip
Instead of editing the request manually, you can use an on-line tool for converting a normal string into a quoted
one.
Request
Content-Type: application/json
Permissions: You must have a system as administrator with an assigned Manage Tenant Configuration role. For
more details about how to add a system as administrator and assign administrator roles, see Add System as
Administrator [page 144], and Edit Administrator Authorizations [page 146].
Request Example
[{
"resourceType": "RESOURCE_I18N_BUNDLE",
"locale": "en",
"contentType": "text/html;charset=UTF-8",
"data": "registerSuccess.thankyou=Thank you for registering with {0}\n
registerForm.validation.accept.privacy.statement=To accept the privacy statement,
click the box above\n
registerSuccess.activateAccount=To activate your account, click the link contained
in the e-mail. Note that it might take a few minutes for the e-mail to reach your
inbox.\n
accountActivation.ui.label.activationsuccesstext=Thank you for registering and
activating your account\n
accountActivation.ui.label.activationtext=\n
createForgottenPasswordMail.user=E-Mail\n
logon.ui.label.user=E-Mail\n
logon.ui.label.forgotpassword=Forgot/Reset Password\n
Response
415 Unsupported Media Type The REST service does not support the
API version requested by the REST cli
ent.
The Change Master Data Texts REST API of SAP Cloud Platform Identity Authentication service can be used to
change the predefined master data for each resource in Identity Authentication.
Prerequisites
To call the methods of this Change Master Data Texts REST API you must have a system as administrator with an
assigned Manage Tenant Configuration role. For more details about how to add a system as administrator and
assign administrator roles, see Add System as Administrator [page 144], and Edit Administrator Authorizations
[page 146].
Usage
The predefined master data represents records in Identity Authentication that contain all relevant system data
about a resource (Salutations, Functions, Departments, Company Relationships, Industries, Languages,
Countries). That data can be used by the system for different classifications in the organization, for example, job
titles, departments, or countries. The predefined master data texts are stored in properties files which can be
downloaded from the links in the table below.
The example below shows the customized values of the Functions file. The dropdown list in the Job Function field
on the Registration form shows the new values that have overwritten the predefined texts in the file.
● Use the GET method to obtain the texts that you have already overwritten in the predefined master data
texts, change the texts that you want, add them to the POST request and upload them.
● Use the GET method to obtain the texts that you have already overwritten in the predefined master data
texts, delete a key value pair, add the texts without this line to the POST request and upload them. This will
replace the deleted key value pair with the predefined one.
● Download the respective properties file from the link in the table, use the GET method to obtain the texts
that overwrote part of the predefined master data texts when your custom tenant was created, from the
downloaded file copy the key value pairs that were not included in the response, change the texts in the
copied key value pairs, add these new key value pairs to the POST request, and execute it.
● Download the respective properties file from the link in the table, copy it to the POST request, and execute
it. This will replace all texts with the predefined ones.
When overwriting data texts, the keys for the different languages must be one and the same. For example, the
master data texts for the German locale are overwritten, and the tenant administrator wants to overwrite the
texts for the French locale. The keys for the German locale should be obtained first and used as keys for the
French locale. After that the values can be translated in French.
Methods
Table 73:
HTTP Method See URI
Note
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Download the texts that you have already overwritten in the predefined master data texts.
Request
URL Parameters
Table 74:
Parameter Required Description Notes
setId No The identifier of the scenario that the re The default value is
source is related to. SAP_DEFAULT
● RESOURCE_MD_SALUTATIO
NS
● RESOURCE_MD_FUNCTIONS
● RESOURCE_MD_DEPARTMEN
TS
● RESOURCE_MD_RELATIONS
HIPS
● RESOURCE_MD_INDUSTRIE
S
● RESOURCE_MD_LANGUAGES
● RESOURCE_MD_COUNTRIES
locale Yes The locale of the resource. The default languages are:
● Chinese (zh)
● Russian (ru)
● Portuguese (pt)
● Polish (pl)
● Dutch (nl)
● Korean (ko)
● Japanese (ja)
● Italian (it)
● French (fr)
● Spanish (es)
● English (en)
● German (de)
● Welsh (cy)
Request Example
GET /service/resource?resourceType=RESOURCE_MD_SALUTATIONS&locale=en
Content-Type: application/json
415 Unsupported Media Type The REST service does not support the
API version requested by the REST cli
ent.
Response Example
Example of response that returns overwritten values of the Salutations file.
{
0001=Dr.,
0002=Prof.
}
Example of response that returns overwritten keys of the Salutations file. The keys can differ than the original in
the master data file. It is not necessary to be in sequence.
{
01=Ms.,
05=Mr.
}
Caution
Make sure that you have applied the proper escaping in your POST request.
You should add \n at the end of each line in the data property content.
\n New line
\r Carriage return
\t Tab
\\ Backslash character
Tip
Instead of editing the request manually, you can use an on-line tool for converting a normal string into a quoted
one.
Request
Permissions: You must have a system as administrator with an assigned Manage Tenant Configuration role. For
more details about how to add a system as administrator and assign administrator roles, see Add System as
Administrator [page 144], and Edit Administrator Authorizations [page 146].
Request Example
https://<tenantId>.accounts.ondemand.com/service/resource/SAP_DEFAULT
Content-Type: application/json
Body:
[{
"resourceType": "RESOURCE_MD_DEPARTMENTS",
"locale": "en",
Response
415 Unsupported Media Type The REST service does not support the
API version requested by the REST cli
ent.
The following table lists error codes that may be returned from any method on any resource URI.
415 Unsupported Media Type The REST service does not support the
API version requested by the REST cli
ent.
This document describes how service providers that delegate authentication to SAP Cloud Platform Identity
Authentication service can use embedded frames, also called overlays, for the logon pages of their applications.
Context
The use of overlays maintains the application context, by keeping the application page as dimmed background, to
provide for minimum disturbance to the work flow. By default, after a successful logon via an overlay page, the
application's parent page reloads. For more information how to configure that option, see Enable or Disable
Reload Parent Page Option [page 60].
Note
When the application uses overlay for the logon page, but the client's browser does not accept third party
cookies, the logon page opens in a fullscreen window.
To open the logon page of the application in an overlay instead of in a fullscreen window when the browser is
set not to accept third party cookies, the user has to add an exception for the domain of this application. The
users can consult the documentations of the different browsers for more information about how to enable third
party cookies for specific websites and domains.
Procedure
Sample Code
○ SAP_IDS.js
Use the following pattern:
Sample Code
Note
The logon link must be an HTML anchor with the following attributes:
attribute value
rel IDS_login
Sample Code
Next Steps
Protect applications against clickjacking when using overlays. For more information, see Configure Clickjacking
Protection [page 250].
Locale
If the locale is known, this can be communicated to Identity Authentication by adding a locale parameter to
SAP_IDS.js.
Source Code
Note
The locale parameter follows the Java specifications for a locale and must be of the format ll_CC where:
Clickjacking is an attempt to trick users into clicking hidden user interface elements without the user realizing it.
The user thinks he or she is clicking on the underlying frame, but is actually clicking on an action chosen by the
attacker.
You have two options to protect your applications against clickjacking when using embedded frames, also called
overlays, for the logon pages of the applications:
● If the applications are SAP UI5 or Web Dynpro, or they use the overlays of SAP Cloud Platform Identity
Authentication service, add the domains of these applications as trusted in the administration console for
Identity Authentication. For more information, see Configure Trusted Domains [page 80].
● If the applications are not SAP UI5 or Web Dynpro, or they do not use the overlays of Identity Authentication,
add the following code to your message handler:
Sample Code
function_messageHandler(oEvent){
if(oEvent.data=='SAPFrameProtection*require-origin'){
oEvent.source.postMessage('SAPFrameProtection*parent-origin','*');
}
}
This section is to help developers with solutions to the REST API response codes.
Error Codes
Table 81:
Response Code Meaning Description
415 Unsupported Media Type The REST service does not support the
API version requested by the REST cli
ent.
Table 82:
User Management REST API PASSWORD_LOCKED The password is locked for 60 minutes
after 5 failed logon attempts with wrong
value.
Success Codes
Table 83:
Response Code Meaning Description
Related Information
This document contains recommendations about how administrators should secure SAP Cloud Platform Identity
Authentication service.
Before you secure Identity Authentication, you should protect the cloud application that trusts Identity
Authentication. For more information about protecting SAP Cloud Platform applications, see Securing
Applications.
User Administration
Set user permissions in accordance with the scenario you are configuring. For more information, see Scenarios
[page 20].
For more information about the settings for user application access, see Configure User Access to the Application
[page 67].
User Authentication
Identity Authentication protects your users during authentication in the following ways:
Password Security
Identity Authentication does not store plain text passwords in the database, but only their iterated random-salted
secure hash values. The random salt is at least 512 bits, and it is different for each password. Only generic hash
Identity Authentication can use also passwords from on-premise systems for user authentication. These
passwords are not stored by Identity Authentication. It sends the user ID and the password for authentication to
the on-premise system via the SSL connection. The management of these passwords depends on the integrated
on-premise system, that supports them, for example Microsoft Active Directory.
Identity Authentication supports three levels of password security. You should use the highest level of security
that matches the requirements of your application. The passwords are managed based on password policy rules.
For more information, see Password Policies [page 102].
Session Security
Session cookies in Identity Authentication are protected with a Secure Socket Layer (SSL) and with the Secure
and HttpOnly attributes. You do not need to make any additional configurations for Identity Authentication.
All communication channels are protected with SSL, and you should configure the cloud application to use SSL
and to check the SAML 2.0 signature.
Data storage security is about how Identity Authentication protects its own database. Data storage security is
ensured by the isolated tenant that each customer receives. Only tenant-specific requests can access the
tenant’s database. These requests are performed by a tenant service, which works with a dependency injection
framework and makes sure that all the services, for example the persistence service and the mail service, are
injected with the instances dedicated to the given tenant.
You can download a CSV file with a history of operations performed by administrators. For more information, see
Export Change Logs with a History of Administration Operations [page 173].
Related Information
You can integrate SAP Cloud Platform Identity Authentication service with SAP and non-SAP systems as service
providers.
Related Information
Context
In this setup, SAP Cloud Platform acts as a service provider, and SAP Cloud Platform Identity Authentication
service acts as an identity provider. For the integration, you must set the trust on both sides.
As a result of the trust setting, when you have deployed an application to SAP Cloud Platform that has protected
resources and requires SAML authentication, the user is redirected to the logon page of SAP Cloud Platform
Identity Authentication service to provide credentials.
Note
Once setting Identity Authentication as a trusted identity provider for SAP Cloud Platform all the services in the
SAP Cloud Platform would be authenticated via Identity Authentication. For more information about the
services provided by SAP Cloud Platform, see Services.
For the integration you need to make configurations in the cockpit of SAP Cloud Platform and in the
administration console for Identity Authentication. The configurations made in the administration console do not
affect the authentication for the cockpit, which is carried out via the SAP-defined tenant, SAP ID service.
Once you purchase an account of SAP Cloud Platform, an e-mail is sent to the contact person from your company
with a link to your SAP Cloud Platform cockpit. The contact person is specified in the Order Form for SAP Cloud
Services. He or she is the first account member of the SAP Cloud Platform cockpit.
Note
For more information how to add other users for the account, see Managing Members
The cockpit is the central point for managing all activities associated with your cloud-based business applications.
For more information about the cockpit, see Cockpit.
To deploy applications on SAP Cloud Platform and to make configurations in the cockpit, you need an account
that corresponds to your role. For more information, see Getting an Account.
SAP Cloud Platform Identity Authentication service does not use for authentication the users registered in the
SAP Service Marketplace, but maintains an own user store for administrators and users.
Once you purchase an account of SAP Cloud Platform, a user account forIdentity Authentication is created for the
same contact person, specified in the Order Form. The contact person is the first administrator in the
administration console for Identity Authentication. He or she receives an activation e-mail for the administration
console account. The subject of the e-mail is: Activate Your Account for Administration Console. Following the
required steps, the administrator activates the account and can continue to the administration console for
Identity Authentication via the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The URL is in the activation e-mail received by the
first administration contains the tenant ID.
Caution
If new SAP Cloud Platform members are added into the Members page of the SAP Cloud Platform cockpit
these members are not added as administrators of Identity Authentication, as this is done only for the first
account member. For more information about how to add new administrators in Identity Authentication, see
Add User as Administrator [page 143].
Prerequisites
Note
If you want to use SAP Cloud Platform in a productive landscape, you should purchase a customer account
or join a partner account. The trial account for SAP Cloud Platform uses the default SAP tenant.
By default, SAP Cloud Platform uses SAP ID service as a trusted identity provider. SAP ID service
is an SAP-defined tenant that cannot be configured by external administrators. If your landscape contains
SAP applications such as SAP Jam, SAP Community Network or Success Map that use authentication
through SAP ID service, you can use the default tenant.
Context
Table 84:
Add a tenant of Identity Authentication registered for your Follow the procedure in: ID Federation with a Identity
company or organization as an identity provider. Authentication Tenant
Note
In this case, the trust is established automatically upon
registration in both the SAP Cloud Platform and the
Identity Authentication tenant. Automatically the SAP
Cloud Platform Account is registered as an application in
the tenant of Identity Authentication. You can find it in the
administration console under the CUSTOM APPLICATIONS
list, representing your SAP Cloud Platform account.
Tip
Once setting Identity Authentication as a trusted identity provider for SAP Cloud Platform all SAP Cloud
Platform applications and services use the trust and configuration settings. If you need different settings for
the different SAP Cloud Platform applications or services, open a new account. For more information, see
Creating Accounts. Once you have created the new account, add the tenant of Identity Authentication in the
new account, and repeat the procedure in the table above to set the trust for each account.
Prerequisites
Context
This configuration is needed if you have added a tenant of Identity Authentication which is not registered for the
organization or company for which the SAP Cloud Platform account is created.
If you have added a tenant of Identity Authentication registered for your company or organization as an identity
provider, see Configure SAP Cloud Platform [page 257].
1. Set the trust with SAP Cloud Platform. For more details, see Configure a Trusted Service Provider [page 35]
2. Optional: Customize the settings for the application. For more information, see Configure Applications [page
26].
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Related Information
Procedure
1. In your Web browser, open the SAP Cloud Platform cockpit using the following URLs:
○ Europe: https://account.hana.ondemand.com/cockpit
○ United States: https://account.us1.hana.ondemand.com/cockpit
○ Australia: https://account.ap1.hana.ondemand.com/cockpit
2. Select the customer account and choose TRUST in the navigation bar.
3. Choose the Trusted Service Provider the identity provider that the platform uses for authentication .
* *
Note
This specifies that all assertion attributes will be mapped to the corresponding principal attributes without
a change
The Assertion Attribute field is for the attribute that comes from the SAML Assertion.
The Principal Attribute field is the user attribute that the users will have at SAP Cloud Platform.
Related Information
You can make your SAP Cloud Platform applications accessible on your own domain different from
hana.ondemand.com - for example www.myshop.com.
Prerequisites
You have configured your application's custom domain using the SAP Cloud Platform console client. For more
information, see Configuring Custom Domains.
Context
When a custom domain is used, both the domain name and the server certificate for this domain are owned by the
customer.
To use a custom domain for the application that uses your SAP Cloud Platform Identity Authentication service
tenant for authentication, follow the procedure as described in the current document.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Once the configuration has been changed, the system displays the message Application <name of
application> updated. The application can only be accessed via the custom domain.
You can use SAP Cloud Platform Identity Authentication service as identity provider for SAP Web IDE.
Prerequisites
Context
The integration between SAP Web IDE and Identity Authentication enables users to access SAP Web IDE with
their Identity Authentication credentials.
SAP Web IDE access can be protected by permissions. To grant a user the permission to access a protected
resource, you can either assign a custom role or one of the predefined virtual roles to such a permission. The
following predefined virtual roles are available:
If you want to use the AccountDeveloper or AccountAdministrator role to enable users to access SAP Web
IDE with their Identity Authentication credentials, see Assign AccountAdministrator or AccountDeveloper Roles
[page 263].
Context
If you want to use the AccountDeveloper or AccountAdministrator role together with SAP Cloud Platform
Identity Authentication service as an identity provider, complete the following steps:
Procedure
1. Access the SAP Cloud Platform with the cockpit administrator role.
Note
For more information how to check the User ID, see List and Edit User Details [page 122]. The User ID is a
six-digit number preceded by the letter P.
Results
The assigned users can log on to SAP Web IDE with their credentials for SAP Cloud Platform Identity
Authentication service (e-mail and password).
Context
If you want to use the Everyone role together with SAP Cloud Platform Identity Authentication service as an
identity provider, complete the following steps:
Procedure
1. Access the SAP Cloud Platform with the cockpit administrator role.
Results
Users can log on to SAP Web IDE with their credentials for SAP Cloud Platform Identity Authentication service (e-
mail and password).
Context
When you use SAP Cloud Platform Identity Authentication service as a trusted identity provider for SAP Web IDE
you can configure the application to display the first name of the user that is logged on in the menu bar and the
welcome screen.
For this scenario, you have to configure the user attribute First Name in SAP Cloud Platform Identity
Authentication service to be sent to SAP Web IDE in the assertion attribute. You also have to configure the First
Name user attribute mapping for Identity Authentication in the SAP Cloud Platform cockpit.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Procedure
1. In your Web browser, open the SAP Cloud Platform cockpit using the following URLs:
○ Europe: https://account.hana.ondemand.com/cockpit
○ United States: https://account.us1.hana.ondemand.com/cockpit
○ Australia: https://account.ap1.hana.ondemand.com/cockpit
2. Select the customer account and choose TRUST in the navigation bar.
3. Choose the Trusted Service Provider subtab, and then choose the identity provider that SAP Web IDE uses for
authentication.
first_name firstname
Note
The Assertion Attribute field is for the attribute that comes from the SAML Assertion.
The Principal Attribute field is the user attribute that the users will have at SAP Cloud Platform.
Once the user has been successfully authenticated to SAP Web IDE, his or her name will appear in Menu bar on
the right.
You can use SAP Cloud Platform Identity Authentication service as identity provider for SAP Document Center.
Prerequisites
Context
The integration between SAP Document Center and Identity Authentication enables users to access SAP
Document Center with their Identity Authentication credentials.Identity Authentication users must be assigned to
the specific Web roles for SAP Document Center. The specific roles contain the access authorizations for the user
interfaces (UIs). For more information about the specific Web roles of SAP Document Center see, Assigning Users
to Roles
The configuration steps are done in the administration console of Identity Authentication and in the cockpit of
SAP Cloud Platform.
Context
You can use Java EE roles to define access to SAP Document Center. You can assign the respective roles for SAP
Document Center to users or to groups of users of SAP Cloud Platform Identity Authentication service. For more
information about the specific web roles for SAP Document Center, see Assigning Users to Roles.
Context
Assign the respective roles for SAP Document Center to individual users of Identity Authentication.
Procedure
1. In the SAP Cloud Platform cockpit with the cockpit administrator role.
Note
You can log on to the cockpit at the URLs given below. Use the relevant URL for your associated region:
○ Europe: https://account.eu1.hana.ondemand.com/cockpit
○ United States: https://account.us1.hana.ondemand.com/cockpit
○ Asia-Pacific: https://account.ap1.hana.ondemand.com/cockpit
Tip
Choose Enable if the service is not enabled for this account.
Results
The assigned user can log on to SAP Document Center with their credentials for Identity Authentication.
Assign the respective roles for SAP Document Center to collections of users of Identity Authentication instead of
individual users. Groups allow you to easily manage the role assignments.
Assertion-based groups are groups determined by values of attributes in the SAML 2.0 assertion.
Procedure
1. Assign a group to users of Identity Authentication. For more information, see Assign Groups to a User [page
129].
For example, you can have a group EVERYONE for all the users of Identity Authentication, and a group
DocCenter_Admins just for the administrators. In this case you should assign the group EVERYONE to all the
users of Identity Authentication, and just the administrators to the DocCenter_Admins group.
2. Configure the groups attribute that is sent to SAP Document Center in the SAML 2.0 assertion. For more
information, see Configure the User Attributes Sent to the Application [page 38]
3. In the cockpit of SAP Cloud Platform define the assertion based groups for the group-to-role mapping in the
cockpit. For more information, see 4. (If Using an Identity Provider) Define the Group-to-Role Mapping.
All users that are members of the group can access SAP Document Center.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Related Information
Procedure
1. In your Web browser, open the SAP Cloud Platform cockpit using the following URLs:
○ Europe: https://account.hana.ondemand.com/cockpit
○ United States: https://account.us1.hana.ondemand.com/cockpit
○ Australia: https://account.ap1.hana.ondemand.com/cockpit
2. Select the customer account and choose TRUST in the navigation bar.
3. Choose the Trusted Service Provider the identity provider that the platform uses for authentication .
* *
Note
This specifies that all assertion attributes will be mapped to the corresponding principal attributes without
a change
The Assertion Attribute field is for the attribute that comes from the SAML Assertion.
The Principal Attribute field is the user attribute that the users will have at SAP Cloud Platform.
Related Information
SAP Identity Management can provision users to and from SAP Cloud Platform Identity Authentication service via
the Identity Authentication connector. For more information about the setting up of an Identity Authentication
system, see Setting up an Identity Authentication System.
SAP Cloud Platform Identity Authentication service is part of the application gallery of Microsoft Azure Active
Directory (Azure AD) under the name SAP HANA Cloud Platform Identity Authentication. For more information,
see SAP HANA Cloud Platform Identity Authentication .
The integration between Identity Authentication and Azure AD is to provide single sign-on (SSO) between
applications that use Azure AD as an authenticating identity provider and applications that use Identity
Authentication as a proxy identity provider.
Prerequisites
Overview
In this scenario Identity Authentication acts as a proxy identity provider and Azure AD as the main authentication
authority for the applications. The authentication requests sent to Identity Authentication are redirected to Azure
AD. User management and authentication is done on Azure AD side.
Note
Users who are in the Azure AD user store can use the single sign-on (SSO) functionality.
Users who are provisioned to Identity Authentication, but not to Azure AD are not able to log on.
Tip
Identity Authentication supports the Identity Federation option. This option allows the application to check if
the users authenticated by the corporate identity provider exist in the user store of Identity Authentication.
In the default setting, the Identity Federation option is disabled. If Identity Federation is enabled, only the
users that are imported in Identity Authentication are able to access the application. For more information
about how to enable or disable Identity Federation with Identity Authentication, see Enable Identity
For this scenario, the configurations are made in the administration console for Identity Authentication and in
Azure classic portal.
Prerequisites
● You have a subscription for Identity Authentication. For more information how to get Identity Authentication,
see Get Started [page 19].
Context
To use Identity Authentication as a proxy, create and configure Azure AD as a corporate identity provider in the
administration console for Identity Authentication. This corporate identity provider is used as an authenticating
authority for the applications.
Procedure
1. Access the tenant's administration console for SAP Cloud Platform Identity Authentication service by using
the console's URL.
Note
The URL has the https://<tenant ID>.accounts.ondemand.com/admin pattern.
Tenant ID is an automatically generated ID by the system. The first administrator created for the tenant
receives an activation e-mail with a URL in it. This URL contains the tenant ID.
Note
If you have an Azure AD corporate identity provider in your list, choose it, and proceed with its
configuration. Type the name of the identity provider in the search field to filter the list items.
Field Information
Single Sign-On Endpoint URL Provide the URL of the identity provider single sign-on
endpoint that receives authentication requests. For
Binding, choose the one that corresponds to respective
single sign-on endpoint.
Single Logout Endpoint URL Provide the URL of the identity provider's single logout
endpoint that receives logout messages. For Binding,
choose the one that corresponds to respective single
logout endpoint.
Tip
Find the information necessary for the manual configuration in the metadata of Azure AD.
Next Steps
1. Choose MS ADFS 2.0 as the type for the configured corporate identity provider. For more information, see
Choose Identity Provider Type [page 163].
2. Select the configured identity provider as the authenticating identity provider for the desired application. For
more information, see Choose Identity Provider for an Application [page 73].
Context
For the configuration of Microsoft Azure AD see Tutorial: Azure Active Directory integration with SAP HANA Cloud
Platform Identity Authentication .
This document is to help users, administrators, and developers deal with issues from SAP Cloud Platform Identity
Authentication service.
You can create an Incident on SAP Support Portal with a component BC-IAM-IDS.
Related Information
SAP Cloud Platform Identity Authentication service has production releases (updates) every second Monday. For
more information about the features delivered every takt, see the Release Notes for Identity Authentication [page
5] published regularly.
To receive regular information about landscape downtimes and news, you need to subscribe to the mailing list of
SAP Cloud Platform. For more information, see Platform Updates and Notifications.
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).