2667924 - Access denied to resource ... on system ... In case this was a valid request, ensure to expose the resource correctly in your cloud connector.

A BTP cloud application fails to connect to a backend system that was exposed in SAP Cloud Connector mapping (SCC -> "Cloud to On-Premise" -> "ACCESS CONTROL"), and from SCC trace (ljs_trace.log (<2.17) /  scc_core.trc (>=2.17)), you perceive one of the following errors:

• "Access denied to resource ... on system ... In case this was a valid request, ensure to expose the resource correctly in your cloud connector";
  
  
• "Access denied to system <hostname:port> In case this was a valid request, ensure to expose the system correctly in your cloud connector";
  
  
• "[RFC] error open connection: Opening connection to backend failed: Opening connection to <hostname:port> denied. Expose the system in your Cloud Connector in case it was a valid request".
  
  
  

Some applications may also raise a Forbidden response (HTTP Status Code 403), while in the cloud connector trace (ljs_trace.log / scc_core.trc) with DEBUG level, the below message is visible:

• "Mapping for virtual host <hostname:port> not found"
  
  

SAP Cloud Connector release independent.

Access, denied, resource, backend, cloud connector, mapping , Acccess denied to system , Request failed with status code 403, Acccess denied to resource , on system,  Backend is not available in the list of defined system mappings in Cloud connector, access denied, resource, Loction Id, multiple sub-accounts, same location id , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-CP-CON , Cloud to On-premise Connectivity service , DS-DI-CON , Connections , Problem