XSHTTPDest
Overview
In SAP HANA XS Classic the concept of destinations is represented with a declarative definition in an .xshttpdest file and optional OAuth configurations. Administrative tasks are available in the XS Admin UI and require special privileges. XSK leverages the SAP BTP Destination service with which these configurations are externalized from the application, thus separating their lifecycle.
Transition path
Below are all artifacts from XS Classic related to destination configuration and how to move them to SAP BTP Destination service.
xshttpdest
Warning
Artifact not supported. Destinations can be created in the SAP BTP Destination service.
| SAP HANA XS Classic | SAP BTP Destination service |
|---|---|
| host | set explicitly as part of URL |
| port | set explicitly as part of URL |
| useSSL | set protocol explicitly as part of URL |
| description | availabe |
| sslAuth | available when using client certificate authentication |
| sslHostCheck | available as TrustAll |
| pathPrefix | set explicitly as part of URL |
| authType | changed to Authentication - see options |
| samlProvider | not available |
| samlACS | not available |
| samlAttributes | not available |
| samlNameId | availabe as nameIdFormat when using SAML Assertion or OAuth SAML Bearer Assertion |
| proxyType | use Internet when connecting to services on the Internet and OnPremise when accessing systems through Cloud Connector |
| proxyHost | not needed |
| proxyPort | not needed |
| timeout | not available - configured explicitly on client level |
| remoteSID | available as RecipientSID using SAP Assertion SSO Authentication |
| remoteClient | available as RecipientClient using SAP Assertion SSO Authentication |
| oAuthAppConfig | mandatoryScopes can be set when using any of the OAuth flows - ie see OAuth Client Credentials Authentication |
xsoauthappconfig
Documentation in SAP Help Portal
Warning
Artifact not supported.
Scopes can still be defined - use any of the OAuth flows and set the scope property in order to achieve the same as with mandatoryScopes ie see OAuth Client Credentials Authentication
| SAP HANA XS Classic | SAP BTP Destination service |
|---|---|
| description | description can be set on destination level |
| clientConfig | not available - configuration specific for each destination |
| mandatoryScopes | if scope list is set on destination level they will be mandatory |
| optionalScopes | not available - if scope list is set on destination level they will be mandatory |
| modifies | not available |
xsoauthclientconfig
Documentation in SAP Help Portal
Warning
Artifact not supported. Some of the properties are available as explicit configuration in the SAP BTP Destination service.
| SAP HANA XS Classic | SAP BTP Destination service |
|---|---|
| clientFlavor | see xsoauthclientflavor on how to configure properties for each destination |
| clientID | set per destination when using any of the OAuth flows |
| clientAuthType | use tokenServiceUser and tokenServicePassword for basic. See OAuth with X.509 Client Certificates for cert |
| authorizationEndpointURL | not available |
| tokenEndpointURL | available as tokenServiceURL when using any of the OAuth flows |
| revocationEndpointURL | not available |
| flow | saml2Bearer - see other types here |
| description | available on destination level |
| samlIssuer | available as assertionIssuer when using SAML Assertion |
| redirectURL | not available - handle authCode flow in code |
| scopeReq | not available |
| shared | not available |
| modifies | not available |
xsoauthclientflavor
Documentation in SAP Help Portal
Warning
Artifact not supported. Headers and query parameters can be defined as described in the SAP BTP Destination service documentation
Reference
SAP Help Portal
For more information, see Destination Administration.
Usage
To use destinations in your project, an instance of Destination service must be created and bound to the XSK environment - see Using Services in the Kyma Environment
After an instance of SAP BTP Destination service is bound to XSK, all destinations will be read from it when using $.net.http.readDestination
Importing destinations
Destinations can be imported directly in SAP BTP Destination service, but as the fields are different, some preprocessing is needed
description = "My Destination";
host = "example.com";
port = 443;
proxyType = none;
proxyHost = "proxy";
proxyPort = 8080;
authType = basic;
useSSL = true;
timeout = 30000;
sslHostCheck = false;
sslAuth = anonymous;
Description = My Destination
Name = My Destination
Type = HTTP
URL = https://example.com:443
ProxyType = Internet
Authentication = BasicAuthentication