-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update from SAP DITA CMS (squashed):
commit e09b2ef70ef7ff2337fcb92920cadf6197677139
Author: REDACTED
Date: Tue Oct 29 09:03:48 2024 +0000
Update from SAP DITA CMS 2024-10-29 09:03:48
Project: dita-all/slu1713332208086
Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap
Output: loiocc0ab4c7365e43bbbee9eae27deb32da
Language: en-US
Builddable map: 446771d4951c4a6988252269c21d94ba.ditamap
commit e80a9ae4a8dcb7da62087c04615fd2af709d1b6a
Author: REDACTED
Date: Tue Oct 29 08:36:50 2024 +0000
Update from SAP DITA CMS 2024-10-29 08:36:50
Project: dita-all/slu1713332208086
Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap
Output: loiocc0ab4c7365e43bbbee9eae27deb32da
Language: en-US
Builddable map: 446771d4951c4a6988252269c21d94ba.ditamap
commit a5c77adafc4d3c1647f30c0929f75f6d3b006730
Author: REDACTED
Date: Tue Oct 29 08:22:14 2024 +0000
Update from SAP DITA CMS 2024-10-29 08:22:14
Project: dita-all/slu1713332208086
Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap
Output: loiocc0ab4c7365e43bbbee9eae27deb32da
Language: en-US
Builddable map: 446771d4951c4a6988252269c21d94ba.ditamap
##################################################
[Remaining squash message was removed before commit...]- Loading branch information
1 parent
8605e6d
commit 25bb478
Showing
302 changed files
with
6,607 additions
and
3,738 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
80 changes: 80 additions & 0 deletions
80
...ate-service-instance-that-contains-deprecated-client-x509-grant-type-0a38373.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| <!-- loio0a383737f6cd4abfb3f1c58680747152 --> | ||
|
|
||
| # Update Service Instance that Contains Deprecated client\_x509 Grant Type | ||
|
|
||
| This information is relevant for you when you operate scenarios using Cloud Integration inbound authentication with client certificates and service instances with client\_x509 grant type. This affects all users who have set up such a scenario before March 2022. | ||
|
|
||
| For SAP Cloud Integration, the client\_x509 grant type has already been removed from the SAP BTP cockpit user interface in March 2022. | ||
|
|
||
| By the end of 2024, grant-type *client\_x509* is deprecated. Grant type *client\_x509* was required to call Cloud Integration endpoints with an *External Certificate* \(see [Creating Service Instance and Service Key for Inbound Authentication](creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md)\). It is substituted by the *client\_credentials* grant type. While service instances with *client\_x509* grant type continue to work, its recommended to replace existing *client\_x509* service instances. To do this, replace the *client\_x509* grant type by *client\_credential* grant type. | ||
|
|
||
|
|
||
|
|
||
| <a name="loio0a383737f6cd4abfb3f1c58680747152__section_osh_w33_rcc"/> | ||
|
|
||
| ## Updating Affected Service Instances | ||
|
|
||
| To find out if a service instance is affected, perform the following steps: | ||
|
|
||
| 1. SAP BTP cockpit and select *Services* \> *Instances and Subscriptions* \> *.* | ||
|
|
||
| 2. Select a service instance. | ||
|
|
||
| > ### Note: | ||
| > Only service instances with service *Process Integration Runtime* are relevant. | ||
| 3. Select *View Parameters*. | ||
|
|
||
|  | ||
|
|
||
| 4. In the popup, choose the *JSON* tab. | ||
|
|
||
| 5. If under *Grant-types* there is the entry *client\_x509*, this service instance is affected. | ||
|
|
||
|  | ||
|
|
||
| 6. Copy the JSON representation to a text editor and replace entry `client_x509` by `client_credentials`. | ||
|
|
||
| 7. Save the text for later reference. | ||
|
|
||
| 8. Create a new service instance and provide the JSON configuration from the text editor. | ||
|
|
||
| 9. For each service key in the old service instance, create a new service key in the new service instance. | ||
|
|
||
| - Open each old service key and copy the value of *certificate* and *certificate-pinning*. You can open a service key by clicking the service key name. This will show the service key details. | ||
|
|
||
| Example: | ||
|
|
||
| ``` | ||
| { | ||
| "oauth": { | ||
| ..., | ||
| ..., | ||
| "certificate": "...", | ||
| "certificate-pinning": "...", | ||
| ..., | ||
| ..., | ||
| ... | ||
| } | ||
| } | ||
| ``` | ||
| - During the creation of the service keys in the new instance, reuse the existing values from the old service instance. The key type must always have the key type *External Certificate*. | ||
| Example: | ||
|  | ||
| - As long as the old service key is not deleted, the creation of the new service key fails with the following error message: | ||
| `Certificate already exists for Follower within Leader with appid […].` | ||
| Resolve this error by deleting the old service key before creating the new service key. | ||
| > ### Note: | ||
| > Deleting a service key means that the client that is using this specific certificate for inbound authentication is no longer able to call integration flow or API endpoints. It is crucial to make sure that a service key with the certificate is recreated in the new service instance. | ||
| See also: [Cloud Integration on CF - How to Setup Secure HTTP Inbound Connection with Client Certificates](https://community.sap.com/t5/technology-blogs-by-sap/cloud-integration-on-cf-how-to-setup-secure-http-inbound-connection-with/ba-p/13393777) \(SAP Community blog\) | ||
Oops, something went wrong.