cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Cloud Connector ; 417 Could not download configuration file.

minchauhan
Discoverer

SAP Cloud Connector 2.12.1.1 4

I'm trying to Create a Subaccount in my SAP Cloud Connector IDE and connect it to my Trail Account but is failing with the error:

417 Could not download configuration file. See ''Log And Trace Files'' and in particular ljs_trace.log for details. Consult SAP note 2460641 for possible remedies

The ljs_trace.log entries are provided below.

As per guidance from previous community posts, calling the the following URL is a Browser returns "Bad Request" https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/a...

The Trial account is set-up :

Provider : Amazon Web Services (AWS)

Region : Europe (Frankfurt) - AWS

Please advise how this should be corrected .

Thanks Min

--------------------------------------------------

https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/a...

2021-01-28 12:22:09,728 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Returned Http Response with code 400|

2021-01-28 12:22:09,728 +0000#INFO#com.sap.scc.config#http-bio-8443-exec-9# #Stopping service channels on 1ef01cc3trial@cf.eu10.hana.ondemand.com|

2021-01-28 12:22:09,728 +0000#WARN#com.sap.scc.rt#http-bio-8443-exec-9# #Tunnel account:///1ef01cc3trial is inoperative. SccEndpoint com.sap.scc.config.TunnelSccEndpoint@795fca38 ok, and context == null|

2021-01-28 12:22:09,732 +0000#ERROR#com.sap.scc.ui#http-bio-8443-exec-9# #SCC handshake failed: 400 — Bad Request com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400 — Bad Request

Accepted Solutions (0)

Answers (2)

Answers (2)

minchauhan
Discoverer
0 Kudos

Can I just confirm, in the following field you suggest using the Long ID ?

If , so this now return the error :

417 An authorization problem occurred when downloading the configuration.

The trace file shows :

2021-01-28 16:43:08,622 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Executing Http Post request to https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/sign/account...

2021-01-28 16:43:10,001 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Returned Http Response with code 403|

2021-01-28 16:43:10,002 +0000#INFO#com.sap.scc.config#http-bio-8443-exec-9# #Stopping service channels on 252f92b1-6271-4b06-8d48-89d2b3ad6c3a@cf.eu10.hana.ondemand.com|

2021-01-28 16:43:10,002 +0000#WARN#com.sap.scc.rt#http-bio-8443-exec-9# #Tunnel account:///252f92b1-6271-4b06-8d48-89d2b3ad6c3a is inoperative. SccEndpoint com.sap.scc.config.TunnelSccEndpoint@35ce6683 ok, and context == null|

2021-01-28 16:43:10,004 +0000#ERROR#com.sap.scc.ui#http-bio-8443-exec-9# #SCC handshake failed: 403 — Forbidden com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 403 — Forbidden

minchauhan
Discoverer
0 Kudos

Is anyone able to provide guidance on this please .

This seems to be a very common problem, and the documentation is not at all clear.

Shashank
Advisor
Advisor
0 Kudos

I too am getting the same error with a particular subaccount. With the same steps I was successfully able to connect with another subaccount but not the one in question. Any clue what might be the reason?

AntalP
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Minesh,

Instead of the subdomain, 1ef01cc3trial you need to provide the ID which is a long number, looks like this one d910002d-400f-4900-8009-ad000000000.

Best regards,

Antal