cancel
Showing results for 
Search instead for 
Did you mean: 

CPI Cloud Connector : Denying Access to system....

prabhu_s2
Active Contributor
0 Kudos

Hi

I am having an access issue with my interface involving cloud connectors...

I have connected the CC and tested it from CC cockpit (connection test) , which works fine. The destination in HANA Cockpit is also working fine but when the interface is executed end-end , i see an issue logged in CC Audit section :

Denying Access to system pdnap.pndlndkop.local:8080

My iFlow [Local work process]:

SOAP RM [Receiver connection]

When i try to select the WSDL for the entry "URL to WSDL", the service and ports are not available for selection. Keying it manually is showing errors. I deduced that this might be due to the SOAP RM protocol and entering the service, endppoints, operation name etc is not required. As i have only one CC, i hope location id is no required in this case [the default is taken @ runtime]

The error logged in iFlow monitoring is:

org.apache.cxf.interceptor.Fault: Could not send Message., cause: org.apache.cxf.transport.http.HTTPException: HTTP response '403: Forbidden' when communicating with http://pdnap.pndlndkop.local:8080/sap/bc/srt/rfc/bic/cfzga_bw_1/150/YPSEL_ORDDTL?MessageId=C54CD8ET-...

1. User id is valid and not locked

2. No trace logged in receiving system

Any pointers on identifying the issue here please?

Thank you

MortenWittrock
Active Contributor

Hi Papp

You have many answered questions with no accepted answer. It's fine to ask many questions, but please do not forget to follow up on your previous questions as well.

Regards,

Morten

Accepted Solutions (1)

Accepted Solutions (1)

r_herrmann
Active Contributor
0 Kudos

Hi prabhu.s2 ,

have you checked the ljs-trace file as described in the following SAP note? https://launchpad.support.sap.com/#/notes/0002473005

Even if the CC Cockpit shows a successful connection, it might be that your destination configuration isn't correct. Either check the ljs trace as described in the above note or (temporary!) switch in Cloud Connector to "Expose Host" which allows access to the system for all paths/urls. If it works via "Expose Host" feature, you can be sure that your destination/path configuration is wrong.

Regards,
Raffael

Answers (0)