Update from SAP DITA CMS (squashed):

commit 866112f00b32b322ad95032b460e4dc37f69d7c2
Author: REDACTED
Date:   Tue Jul 23 20:40:03 2024 +0000

    Update from SAP DITA CMS 2024-07-23 20:40:03
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 48c763db6cb8a5c8ba132d6e71d9a6294902322f
Author: REDACTED
Date:   Tue Jul 23 18:40:13 2024 +0000

    Update from SAP DITA CMS 2024-07-23 18:40:13
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 98183818f86cec7a4c5e68e7c46fd9f2fd9c5bf7
Author: REDACTED
Date:   Tue Jul 23 16:39:48 2024 +0000

    Update from SAP DITA CMS 2024-07-23 16:39:48
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

##################################################
[Remaining squash message was removed before commit...]

docs/10-concepts/apis-d1d1107.md

@@ -6,7 +6,7 @@ Discover and consume APIs to manage, build, and extend the core capabilities of
 
 
 
-An Application Programming Interface or API is an **interface provided by an application for interacting with other applications**. APIs specify how software programs are able to exchange information with each other, even if designed and run by different organizations. They facilitate interaction by selectively exposing certain functionality, allowing different apps, websites, and devices to communicate effectively with each other. More importantly, APIs allow businesses to reach beyond regular business channels and share data, content, and services directly to both B2B \(business to business\) and B2C \(business to consumer\) clients, making UI development easy.
+An Application Programming Interface or API is an **interface provided by an application for interacting with other applications**. APIs specify how software programs are able to exchange information with each other, even if designed and run by different organizations. They facilitate interaction by selectively exposing certain functionality, allowing different apps, websites, and devices to communicate effectively with each other. More importantly, APIs enable businesses to reach beyond regular business channels and share data, content, and services directly to both B2B \(business to business\) and B2C \(business to consumer\) clients, making UI development easy.
 
 
 
@@ -33,7 +33,7 @@ Description
 <tr>
 <td valign="top">
 
-**[SAP BTP on SAP Business Accelerator Hub](https://api.sap.com/products/SAPCloudPlatform/overview)**
+[SAP BTP on SAP Business Accelerator Hub](https://api.sap.com/products/SAPCloudPlatform/overview) 
 
 </td>
 <td valign="top">
@@ -47,26 +47,26 @@ It is also the official place where REST and OData REST API references are publi
 <tr>
 <td valign="top">
 
-**[SAP BTP API Management](https://help.sap.com/viewer/p/SAP_CLOUD_PLATFORM_API_MANAGEMENT)**
+[API Management Capability within SAP Integration Suite](https://help.sap.com/viewer/p/SAP_CLOUD_PLATFORM_API_MANAGEMENT) 
 
 </td>
 <td valign="top">
 
-API Management allows you to build, manage, publish, and monetize your own APIs within one secure and scalable environment.
+With the API Management capability, you can build, manage, publish, and monetize your own APIs within one secure and scalable environment.
 
 </td>
 </tr>
 <tr>
 <td valign="top">
 
-**SDKs**
+**Software Development Kits \(SDKs\)**
+
+For an overview on the available SDKs, see [Tools](tools-abcae5b.md).
 
 </td>
 <td valign="top">
 
-The software development kits \(SDKs\) available for SAP BTP offer APIs to, for example, accelerate enterprise app development.
-
-For an overview on the available SDKs, see [Tools](tools-abcae5b.md).
+The SDKs available for SAP BTP offer APIs to, for example, accelerate enterprise app development.
 
 </td>
 </tr>

docs/10-concepts/bringing-your-corporate-identity-provider-for-platform-users-feature-set-a-783ff50.md

@@ -22,21 +22,21 @@ The following figure illustrates the architecture required for platform users. T
 
 ![](images/architecture_platform_users_features_set_a_14e046f.png "Architecture Required for Custom User Base of Platform Users")
 
-In the preceding figure, you enable trust between SAP BTP and your corporate identity provider over your tenant of SAP Cloud Identity Services - Identity Authentication. For each Neo subaccount, you choose the Identity Authentication tenant to use as the platform identity provider. The Identity Authentication tenant automatically configures an application within the tenant and generates an identifier to establish the connection between the two entities. When you log on to a platform resource, such as the cockpit, you indicate the Neo subaccount you want to log on with using this identifier in the subdomain, for example, `https://cockpit.eu10.hana.ondemand.com/cockpit/?idp=bs8ibxkn.accounts.ondemand.com`. Once you’ve logged on with your platform user, the cockpit displays any global accounts and subaccounts your platform user is a member of.
+In the preceding figure, you enable trust between SAP BTP and your corporate identity provider over your tenant of SAP Cloud Identity Services - Identity Authentication. For each Neo subaccount, you choose the SAP Cloud Identity Services tenant to use as the platform identity provider. The SAP Cloud Identity Services tenant automatically configures an application within the tenant and generates an identifier to establish the connection between the two entities. When you log on to a platform resource, such as the cockpit, you indicate the Neo subaccount you want to log on with using this identifier in the subdomain, for example, `https://cockpit.eu10.hana.ondemand.com/cockpit/?idp=bs8ibxkn.accounts.ondemand.com`. Once you’ve logged on with your platform user, the cockpit displays any global accounts and subaccounts your platform user is a member of.
 
 > ### Note:  
 > An e-mail address alone isn’t enough to determine membership in an account. For Neo subaccounts the identifier is the user base \(identity provider\) and a configurable identifier with the user base; usually the user ID. For multi-environment subaccounts, the identifier is the origin \(your Cloud Foundry-specific alias for the identity provider\) and e-mail address. For example, you can have a platform user in the default identity provider, SAP ID service, and another user in your corporate identity provider with the same e-mail address. You can log on to the cockpit with both, but the cockpit displays different user information. This difference is because you’ve logged on with different identity providers.
 > 
-> You also see this difference when assigning roles or membership in subaccount. You must provide the user base or origin in addition to the e-mail address of the user. You can choose your own origin for multi-environment accounts, but the origin must be unique across all SAP customers. We recommend using the subdomain of your Identity Authentication tenant or your organization's name. All your users must be able to remember or type the origin when they use the Cloud Foundry command-line interface or service dashboards. A string of random characters isn't useful.
+> You also see this difference when assigning roles or membership in subaccount. You must provide the user base or origin in addition to the e-mail address of the user. You can choose your own origin for multi-environment accounts, but the origin must be unique across all SAP customers. We recommend using the subdomain of your SAP Cloud Identity Services tenant or your organization's name. All your users must be able to remember or type the origin when they use the Cloud Foundry command-line interface or service dashboards. A string of random characters isn't useful.
 
 To use a corporate identity provider for platform users of a multi-environment subaccount, you need a Neo subaccount set up for the same corporate identity provider. This requirement exists, because logon to the cockpit is dependent on a Neo subaccount. You’re extending the existing configuration of your Neo subaccount to add the trust of your corporate identity provider to your multi-environment subaccounts.
 
-For Neo subaccounts, there’s a 1:1 relationship between its applications in your Identity Authentication tenant. Multi-environment subaccounts are handled differently. During configuration, you submit a support ticket in which you state all the regions you want to apply this corporate identity provider configuration. This trust then applies to **all** your multi-environment subaccounts in those regions. So, all your multi-environment subaccounts share the same application in your Identity Authentication tenant.
+For Neo subaccounts, there’s a 1:1 relationship between its applications in your SAP Cloud Identity Services tenant. Multi-environment subaccounts are handled differently. During configuration, you submit a support ticket in which you state all the regions you want to apply this corporate identity provider configuration. This trust then applies to **all** your multi-environment subaccounts in those regions. So, all your multi-environment subaccounts share the same application in your SAP Cloud Identity Services tenant.
 
 Configuring platform users for multi-environment subaccounts has no impact on your existing Neo configuration. You need the Neo configuration to log on to resources like the cockpit.
 
 > ### Recommendation:  
-> While support of multiple corporate identity providers is possible, we recommend using your Identity Authentication tenant as a proxy and use conditional authentication to separate them.
+> While support of multiple corporate identity providers is possible, we recommend using your SAP Cloud Identity Services tenant as a proxy and use conditional authentication to separate them.
 
 **Related Information**  
 

docs/10-concepts/bringing-your-corporate-identity-provider-for-platform-users-feature-set-b-8980b91.md

@@ -24,26 +24,24 @@ The following figure illustrates the architecture required for platform users. T
 
 ![](images/SAP_BTP_Account_Mapping_e29be15.png)
 
-In the preceding figure, you enable trust between the SAP BTP global account and your corporate identity provider over your tenant of SAP Cloud Identity Services - Identity Authentication. For each global account, you choose the Identity Authentication tenant to use as the identity provider for platform users. For the platform identify provider, you can have up to three Identity Authentication tenants per global account. Multiple global accounts can share the same Identity Authentication tenant. When you log on to a platform resource, such as the cockpit, you indicate the Identity Authentication tenant that you want to log on with. For example, to log on to the cockpit, copy a URL parameter from the cockpit to identify the tenant:
+In the preceding figure, you enable trust between the SAP BTP global account and your corporate identity provider over your tenant of SAP Cloud Identity Services - Identity Authentication. For each global account, you choose the SAP Cloud Identity Services tenant to use as the identity provider for platform users. For the platform identify provider, you can have up to three SAP Cloud Identity Services tenants per global account. Multiple global accounts can share the same SAP Cloud Identity Services tenant. When you log on to a platform resource, such as the cockpit, you indicate the SAP Cloud Identity Services tenant that you want to log on with. For example, to log on to the cockpit, copy a URL parameter from the cockpit to identify the tenant:
 
 <code>https://cockpit.btp.cloud.sap/cockpit/?idp=<i class="varname">&lt;tenant&gt;</i>.accounts.ondemand.com</code>
 
 For example: `https://cockpit.btp.cloud.sap/cockpit/?idp=cidppuxhm.accounts.ondemand.com`
 
 Once you’ve logged on, the cockpit displays any global accounts and subaccounts of which your platform user is a member.
 
-Typically, a user is identified by email and origin \(your alias for the identity provider\). However, to most accurately identify a user, you need both user identifier and an identifier from an identity provider. The reason is that the system treats users with the same name but from different identity providers as separate users. For example, you can have a platform user in the default identity provider, SAP ID service, and another user in your corporate identity provider with the same e-mail address. This behavior applies to global accounts, directories, multi-environment subaccounts, and Cloud Foundry orgs and spaces.
-
-For Neo subaccounts a user is uniquely identified by the user base \(hostname of the Identity Authentication tenant\) and a configurable subject identifier. You can log on to the cockpit with both, but the cockpit displays different user information. This difference is because you’ve logged on with different identity providers.
+Typically, a user is identified by email and origin \(your alias for the identity provider\). However, to most accurately identify a user, you need both user identifier and an identifier from an identity provider. The reason is that the system treats users with the same name but from different identity providers as separate users. For example, you can have a platform user in the default identity provider, SAP ID service, and another user in your corporate identity provider with the same e-mail address. This behavior applies to global accounts, directories, multi-environment subaccounts, and Cloud Foundry orgs and spaces. A user is uniquely identified by the user base \(host name of the SAP Cloud Identity Services tenant\) and a configurable subject identifier. If this user exists in two identity providers, meaning two user bases, they are considered as two users \(with different authorizations\). Both users can log on to the cockpit. However, their user information is different in Neo subaccounts because they are stored in different identity providers.
 
 > ### Note:  
-> With enhancements of cloud management tools feature set B, the trust configuration between SAP BTP and Identity Authentication changes for platform users \(for example, administrators, developers, operators\) in the Neo environment. The change only applies to global accounts in cloud management tools feature set B which have custom trust configurations for platform users.
+> With enhancements of cloud management tools feature set B, the trust configuration between SAP BTP and SAP Cloud Identity Services - Identity Authentication changes for platform users \(for example, administrators, developers, operators\) in the Neo environment. The change only applies to global accounts in cloud management tools feature set B which have custom trust configurations for platform users.
 > 
 > For more information, see [SAP Note 3330671](https://launchpad.support.sap.com/#/notes/3330671).
 
 You also see this difference when assigning roles. You must provide the origin or user base in addition to the e-mail address or user ID of the user. When platform users use the Cloud Foundry command-line interface or service dashboards, they need to remember the origin. You can choose your own origin, but the origin must be unique across all customers. We recommend that you use a meaningful name that helps identify the target it points to.
 
-In Identity Authentication, there's one application that represents SAP BTP overall. So, if you have multiple global accounts with the same Identity Authentication tenant, they all share the same application in your Identity Authentication tenant that is where customers typically configure settings such as the corporate identity provider used for authentication and user attribute mapping between systems. For more information, see [Map User Attributes from a Corporate Identity Provider for Platform Users](../50-administration-and-ops/map-user-attributes-from-a-corporate-identity-provider-for-platform-users-40c2e54.md).
+In SAP Cloud Identity Services - Identity Authentication, there's one application that represents SAP BTP overall. So, if you have multiple global accounts with the same SAP Cloud Identity Services tenant, they all share the same application in your SAP Cloud Identity Services tenant that is where customers typically configure settings such as the corporate identity provider used for authentication and user attribute mapping between systems. For more information, see [Map User Attributes from a Corporate Identity Provider for Platform Users](../50-administration-and-ops/map-user-attributes-from-a-corporate-identity-provider-for-platform-users-40c2e54.md).
 
 **Related Information**  
 

docs/10-concepts/business-users-2e68494.md

@@ -6,7 +6,7 @@
 
 Application developers \(platform users\) create and deploy application-specific security artifacts for business users, such as scopes. Administrators use these artifacts to assign roles, build role collections, and assign these role collections to business users or user groups. In this way, they control the users' permissions in the application.
 
-For business users, there's a [default identity provider](../50-administration-and-ops/default-identity-provider-d6a8db7.md), too. We expect that you have your own identity provider. We recommend that you configure your custom tenant of Identity Authentication as the identity provider and connect Identity Authentication to your own corporate identity provider.
+For business users, there's a [default identity provider](../50-administration-and-ops/default-identity-provider-d6a8db7.md), too. We expect that you have your own identity provider. We recommend that you configure your custom tenant of SAP Cloud Identity Services as the identity provider and connect SAP Cloud Identity Services to your own corporate identity provider.