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.