Connectivity: Destinations and Cloud Connector

Keep this: job aid

BTP connectivity checklist

• Pick the proxy type: Internet for public targets, OnPremise through the Cloud Connector for private ones.
• One destination name across stages; stage-specific URL, client and credentials; no secrets in code.
• OnPremise URL = virtual host and port exactly as mapped in the Cloud Connector.
• Expose only the API paths each app needs; paths are case-sensitive.
• Track the Cloud Connector subaccount certificate expiry; use HA (master and shadow) for production.
• Technical user for reads and external users; PrincipalPropagation for writes that need the person.
• Propagation setup: trusted IdPs synchronized, system and CA certificates, subject pattern, STRUST, ICM trust, CERTRULE.
• Check Connection proves reachability only; a 401 can still pass it.
• Troubleshoot in order: app, destination, Cloud Connector, back-end reachability, back-end identity.
• Traffic traces only briefly and under control; they can contain sensitive data.