sap-btp-connectivity

Configure SAP BTP destinations, Cloud Connector, and Kubernetes connectivity proxies for hybrid landscapes.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-btp-connectivity-melik1986
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-btp-connectivity
Source: https://github.com/Melik1986/axon-erp-api/tree/main/cursor/skills/sap-btp-connectivity
Command: npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-btp-connectivity-melik1986

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up secure connectivity between SAP BTP applications and cloud or on-premise systems involves many components—Destination Service, Cloud Connector, Connectivity Proxy, and Transparent Proxy—each with complex authentication and configuration requirements that frequently cause errors like HTTP 405, 407, and 503. ## Core Features & Use Cases - Destination Configuration: Create HTTP, RFC, LDAP, MAIL, and TCP destinations with 17+ authentication types including OAuth2ClientCredentials, OAuth2SAMLBearerAssertion, and PrincipalPropagation. - Cloud Connector & Kubernetes Setup: Install and configure Cloud Connector with high availability, plus deploy Connectivity Proxy and Transparent Proxy in Kubernetes/Kyma via Helm. - Troubleshooting & Security: Diagnose common connectivity errors, configure access control, and apply security best practices for hybrid landscapes. - Use Case: You need to expose an on-premise SAP Gateway OData service to a BTP application with single sign-on. Use this Skill to configure the Cloud Connector system mapping, create an OnPremise destination with PrincipalPropagation, and verify the connection. ## Quick Start Ask the AI to create an HTTP destination named 'my-api' with OAuth2ClientCredentials authentication pointing to your target API endpoint.

Frequently Asked Questions about sap-btp-connectivity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an HTTP destination in SAP BTP?▼

Create an HTTP destination in the BTP Cockpit under Connectivity > Destinations by specifying Name, Type HTTP, URL, ProxyType, and Authentication. For OAuth2ClientCredentials, provide clientId, clientSecret, and tokenServiceURL, or import a JSON configuration via the Destination Service REST API.

How to set up Cloud Connector for on-premise connectivity?▼

Install Cloud Connector on Windows, Linux, or macOS, access the admin UI at https://hostname:8443, change the default Administrator/manage password, and add your BTP subaccount. Then configure access control with system mappings and resource paths for each backend system.

What is the difference between Connectivity Proxy and Transparent Proxy?▼

Connectivity Proxy is a Kubernetes component that provides on-premise access through a SOCKS5 proxy on port 20003. Transparent Proxy exposes BTP destinations directly as Kubernetes Services using Destination Custom Resources, simplifying application configuration.

Why am I getting HTTP 503 from Cloud Connector?▼

HTTP 503 indicates the Cloud Connector is offline or unreachable. Verify the connector shows a green connected status for your subaccount, check that the Location ID in your destination matches the connector configuration, and confirm firewall rules allow outbound HTTPS.

Does SAP BTP support principal propagation to on-premise systems?▼

Yes, PrincipalPropagation authentication forwards the business user identity from BTP to on-premise systems via Cloud Connector. The connector generates an X.509 certificate from the user JWT, requiring trust configuration and certificate mapping rules on the backend.

When should I use a reverse proxy instead of Cloud Connector?▼

Use a reverse proxy only when reusing existing ADC infrastructure is mandatory. Cloud Connector is preferred because it avoids exposing services to the internet, supports RFC to older ABAP systems, provides built-in principal propagation, and requires no firewall changes.