Skip to Content

Unable to connect new CF accounts to cloud connector

Hi

We are trying to complete https://developers.sap.com/mission.mobile-dev-kit-level-up.html with a real service, so we try to connect a new SCP CF (AWS Frankfurt) account to our cloud connector. That fails with "417 Could not download configuration file."

When we try to do that with an existing account on CF, it succeeds.

We see a difference in the CF accounts, one seems to be in Rot (old one) and the other in Frankfurt.

Any pointers?

Kind regards

Bart

Add a comment
10|10000 characters needed characters exceeded

Related questions

9 Answers

  • Posted on Apr 21 at 10:25 AM

    Hi Bart,

    Have you used the "long" subaccount ID or the short technical name when adding it in SCC?

    As your subaccount is in CF you need to use the long ID, that you can see in the Cockpit under the Subaccount Details. You should check this.

    Best Regards,

    Viktor

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 21 at 11:18 AM

    Hi Viktor

    We used the long id:

    The logs from SCC:

    2020-04-21 13:20:27,985 +0200#WARN#com.sap.scc.config#http-bio-8443-exec-6# #Creating an sslContextProvider for account 10e7e627-db45-4b1c-8e00-c24f4a865f3b@cf.eu10.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.| 2020-04-21 13:20:28,083 +0200#INFO#com.sap.scc.security#http-bio-8443-exec-6# #Will retrieve Connectivity CA certificate from SAP Cloud Platform| 2020-04-21 13:20:28,084 +0200#INFO#com.sap.scc.security#http-bio-8443-exec-6# #Executing Http Get request to https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/10e7e627-db45-4b1c-8e00-c24f4a865f3b| 2020-04-21 13:20:28,665 +0200#INFO#com.sap.scc.security#http-bio-8443-exec-6# #Returned Http Response with code 500| 2020-04-21 13:20:28,666 +0200#INFO#com.sap.scc.config#http-bio-8443-exec-6# #Stopping service channels on 10e7e627-db45-4b1c-8e00-c24f4a865f3b@cf.eu10.hana.ondemand.com| 2020-04-21 13:20:28,666 +0200#WARN#com.sap.scc.rt#http-bio-8443-exec-6# #Tunnel account:///10e7e627-db45-4b1c-8e00-c24f4a865f3b is inoperative. SccEndpoint com.sap.scc.config.TunnelSccEndpoint@917bf7c7 ok, and context == null| 2020-04-21 13:20:28,666 +0200#ERROR#com.sap.scc.ui#http-bio-8443-exec-6# #SCC handshake failed: 500 — Internal Server Error com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 500 — Internal Server Error at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:140) at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:94) at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:65) at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:142) at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:102) at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1410) at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:183) at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:42) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:23) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:604) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:165) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:1025) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1195) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:654) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:317) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:809)| 2020-04-21 13:20:34,401 +0200#WARN#com.sap.scc.ui#http-bio-8443-exec-3# #cannot read value of field DEBUG of class javax.net.ssl.SSLSocketFactory|


    cf-issue.png (110.4 kB)
    Add a comment
    10|10000 characters needed characters exceeded

    • I am also facing similar issue while connecting cloud connector to Europe(Frankfurt)- AWS region. I am using the Long ID as suggested by you. below are the logs

      2020-04-22 06:53:32,110 +0000#WARN#com.sap.scc.config#http-bio-8443-exec-9# #Creating an sslContextProvider for account account-id@cf.eu10.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.| 2020-04-22 06:53:32,115 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Will retrieve Connectivity CA certificate from SAP Cloud Platform| 2020-04-22 06:53:32,115 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Executing Http Get request to https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/account-id| 2020-04-22 06:53:32,837 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Returned Http Response with code 500| 2020-04-22 06:53:32,838 +0000#INFO#com.sap.scc.config#http-bio-8443-exec-9# #Stopping service channels on account-id@cf.eu10.hana.ondemand.com| 2020-04-22 06:53:32,838 +0000#WARN#com.sap.scc.rt#http-bio-8443-exec-9# #Tunnel account:///account-id is inoperative. SccEndpoint com.sap.scc.config.TunnelSccEndpoint@384c9f4f ok, and context == null| 2020-04-22 06:53:32,840 +0000#ERROR#com.sap.scc.ui#http-bio-8443-exec-9# #SCC handshake failed: 500 — Internal Server Error

  • Posted on Apr 22 at 02:26 PM

    Hi Viktor,

    I am also facing similar issue while connecting cloud connector to Europe(Frankfurt)- AWS region. I am using the Long ID as suggested by you. below are the logs

    2020-04-22 06:53:32,110 +0000#WARN#com.sap.scc.config#http-bio-8443-exec-9# #Creating an sslContextProvider for account @ cf.eu10.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.| 2020-04-22 06:53:32,115 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Will retrieve Connectivity CA certificate from SAP Cloud Platform| 2020-04-22 06:53:32,115 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Executing Http Get request to https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/ | 2020-04-22 06:53:32,837 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Returned Http Response with code 500| 2020-04-22 06:53:32,838 +0000#INFO#com.sap.scc.config#http-bio-8443-exec-9# #Stopping service channels on @ cf.eu10.hana.ondemand.com| 2020-04-22 06:53:32,838 +0000#WARN#com.sap.scc.rt#http-bio-8443-exec-9# #Tunnel account:/// is inoperative. SccEndpoint com.sap.scc.config.TunnelSccEndpoint@384c9f4f ok, and context == null| 2020-04-22 06:53:32,840 +0000#ERROR#com.sap.scc.ui#http-bio-8443-exec-9# #SCC handshake failed: 500 — Internal Server Error

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 30 at 12:00 PM

    Hi Viktor Romasz

    In the cloud connector we are now able to add our new CF-trial instance. We link our system in it and everything is reachable.

    But on the Cloud Foundry SCP instance the Cloud Connector isn't displaying.

    Are there any problems with this?

    Thanks in advance!

    Kind regards,

    Robin

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Robin,

      You should check the active Cloud Connector status in the Connectivity >> Cloud Connectors menu, when the subaccount is connected.
      Could you please upload a screen shot about the status, displayed there?

      Thank you

      Best Regards,

      Viktor

  • Posted on Jun 13 at 03:44 AM

    Hello Robin / Viktor: I am also having the same issue that Robin had (or still is having?)... The Cloud Connector link does not show up in my trial Cloud Foundry SCP account. I, too was successfully able to create a new entry in my Cloud Connector for this Cloud Foundry SCP account; but since there's no Cloud Connector entry to be made in SCP, the destination creation using on-premise cannot work. In my previous two trials of SCP, the Cloud Connector link showed and worked perfectly well; but this trial that began in April 2020 has the issue of no Cloud Connector entry. Please see enclosed screenshots for details...before.png and now.png.


    before.png (76.8 kB)
    now.png (49.6 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 07 at 01:18 PM

    Hi Janoo Bande,

    we are facing the same issue.

    Did you solve it ?

    BR,

    Christiano.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 12 at 11:20 PM

    Unfortunately I have the same issue, any clue?

    Thanks.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 14 at 07:51 AM

    Hi All,

    I was facing the SCC handshake failed error for cc and cockpit.

    I have tried with the following configuration and subaccount created for me for the AWS Frankfurt region.

    region: cf.eu10.hana.ondemand.com

    subaccount: subaccount id (long id) which is mentioned in the subaccount details tab of the cockpit.

    And add email id and password from the user information tab on the cockpit area.

    I hope it will work for all of you as well.

    Thanks.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 15 at 04:21 PM

    Any solution about SCC in CF Trial Account ?. I have the same problem that:

    Robin Panneels Janoo Bande Christiano José Beltrão MagalhãesJhon Jairo Teran Salazar Please any body has a solution in this moment? When I config my SCC (local) with my account its fine!, but there aren't a way to see my systems exposed in CF account because in "connectivity" option we dont have cloud connector option any more. Appreceate your help with this issue or feature???Thanks

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.