Skip to Content
0

How to resolve access denied message from the Cloud Connector

Jun 01, 2017 at 10:49 AM

475

avatar image
Former Member

Hello,

I have the following issue:

I am working in the WebIDE and developing a UI5 Application. I want to consume my Gateway Service from the APG System. But i get the following error message in the Network part (Google Chrome Tools):

My Destination looks like this, is reachable and has all the information it needs (WebIDEUsage : odata_gen, odata_abap, dev_abap, ui5_execute_abap):

My (local(host)!) Cloud Connector Settings are (Cloud To On-Premise):

And the Gateway Service is working fine with the Gateway Client or with transaction SICF.

I am working with my D-User developer account from int.sap.hana.ondemand.com

I already searched and asked (colleagues) for solutions, but no one has an idea.

Can someone from here help me?

Thank you.

access-denied.png (35.6 kB)
destination.png (65.8 kB)
cloud-connector.png (106.8 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Robert Russell Jun 01, 2017 at 12:56 PM
0

Hi Simon,

From the screenshots then you have an odata service with url /sap/zanalyzerservice but no URL path defined for this in your Cloud Connector.
You have many /sap/... but nothing that matches /sap/zanly...

Regards

Robert

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Robert,

thank you for your answer. Mh when i test my service, the service url is http://ldciapg.wdf.sap.corp:50011/sap/opu/odata/sap/zanalyzerservice_srv?sap-client=260. I didn't noticed that he uses only /sap/ in the error messsage.

So when i add /sap as path and allow all other sub-paths, then the error message says: "Service cannot be reached" HTTP 404 - Not found. Same with /sap/zanalyzerservice_srv.

Additional WebIDE information:

My neo-appp.json route properties:

"routes": [

{ "path": "/sap/opu/odata/",

"target":

{ "type": "destination", "name": "APG260"

},

"description": "APG260" }

0
Former Member

I found my problem!

in the neo-app.json i changed my route entry to this:

{

"path": "/sap/opu/odata/",

"target":

{

"type": "destination",

"name": "APG260",

"entryPath": "/sap/opu/odata/"

},

"description": "APG260"

}

0

Hi Simon,

Good to hear you resolved your issue.

May help others if you copy your last reply as an actual answer not a comment. Then close the question. Comments are not that visible on this site as you know :).

Cheers

Robert

1