You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-js/features/connectivity/destination.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,7 +200,7 @@ The SAP Cloud SDK provides a default implementation for the transformation of se
200
200
201
201
The default implementation also retrieves a service token, if needed.
202
202
203
-
Additionally, we provide a default implementation for the transformation of service bindings to OAuth2ClientCredentials destinations.
203
+
Additionally, we provide a function to transform service bindings into OAuth2ClientCredentials destinations, assuming the service binding follows the structure outlined below:
204
204
205
205
It assumes that your service binding is of the following structure:
206
206
@@ -223,7 +223,7 @@ It assumes that your service binding is of the following structure:
223
223
}
224
224
```
225
225
226
-
If your service URL is not in the `url` property, you can alternatively provide a `url` property as part of the `options`object.
226
+
If the service URL is not specified in the `url` property, it can alternatively be provided as part of the `options`parameter.
227
227
228
228
The following is a multi-tenant example, where the user's JWT is used for tenant-isolation in the cache together with a custom URL as target.
0 commit comments