Skip to Content
Product Information
Author's profile photo Marco Ertel

New release of the Cloud Connector (2.13)

A new version of the Cloud Connector with lots of new things is released and ready to download from tools.hana.ondemand.com. Many things have been changed- some are visible, and others are behind the scenes. Let me give you an overview of the most interesting and important changes:

Visually you will see some differences as now Fiori 3 is used and already on the logon screen a long time wish of some customers is implemented:

logon%20screen

Directly on the logon screen you can add helpful information for users of this instance like here on the screenshot on how to get support and much more.

Another cool addition which also adds more information to the UI is the subaccount monitoring for giving you more insights where which calls happen and how much data is transferred for:

With that information performance optimizations will be easier than before. You have access to a performance overview where calls got collected in different buckets from a timing perspective. But also, in more detailed views like the most recent requests or the top time-consuming requests. This information can be found directly in the UI but there are also APIs available that data in other systems. Read more in our documentation.

Other APIs which are new belong to the configuration. As usual more details can be found in the documentation.

A new feature from a networking perspective is the possibility to not only use single ports for TCP (and TCP ssl) but also port ranges which minimizes the number of necessary mappings especially for FTP:

We all know keeping software up to date is not easy. To make it easier for you keeping the Cloud Connector on the most recent version we’ve added a notification and an alert which will inform you as soon as newer versions are released.

Behind the scenes many other changes happened to ensure better security but also to adjust the used software pieces to a newer state like the change on the used tomcat version from 7 to 8.5.

SAP Cloud Connector is already available on several platforms, but we even added now one more: Linux on ppc64 (little endian). If you need more details about the supported platforms have a look.

As usual the current version can be found on tools.hana.ondemand.com and the complete release notes are also worth a look!

Assigned tags

      21 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Ariel Bravo Ayala
      Ariel Bravo Ayala

      Thanks for the update… does this version support ARM-based CPUs? The 2.12.x cc has a C library that is compiled only for x86_64. Thanks!

      Author's profile photo Marco Ertel
      Marco Ertel
      Blog Post Author

      Hi Ariel,

      right now there is no support for ARM-based CPUs as we do not see enough demand to add an additional platform.

      Kind Regards

      Marco

      Author's profile photo Ariel Bravo Ayala
      Ariel Bravo Ayala

      Thanks Marco for the update. I think you will have more demand sooner rather than later, the consumer market is getting flood by powerful arm cpus and I would speculate on an increase in the enterprise sector as well. For example, many SAP employees use apple computers and the new macs have arm based cpus.

      My particular scenario is really a hobby. I’m using Ngrok for now, but it would be great to have a lightweight cloud connector as well. When I tried to make it work (2019), the only obstacle I found was the C library I mentioned, I would guess there are other considerations that I am not aware of.

      Br,

      Ariel

      Author's profile photo Rupali Karbhari
      Rupali Karbhari

      Hi Macro,

      Thank you for sharing details around new features on latest cloud connector release. We are already having 2.12 version installed , additional guidelines on upgrading existing version can help further. Thanks !!

      Author's profile photo Marco Ertel
      Marco Ertel
      Blog Post Author

      Hi Rupali,

      we recommend to upgrade to the actual version as also security fixes and updates of used components are happening.

      Kind Regards

      Marco

      Author's profile photo Rupali Karbhari
      Rupali Karbhari

      Sure. Thanks. Can you share process of upgrade pls.

       

      Best Regards,

      Rupali K

      Author's profile photo Marco Ertel
      Marco Ertel
      Blog Post Author

      Hi Rupali,

      please follow the process described in the documentation.

      Kind Regards
      Marco

      Author's profile photo Rupali Karbhari
      Rupali Karbhari

      Hi Macro - Thank you !! Appreciate your quick response.

      Author's profile photo Naresh Dasika
      Naresh Dasika

      Hello Marco,

      Thanks for the detailed blog.

      With this latest version of Cloud Connector, would it be possible to create multiple user accounts? Current version has some limitation on creation of multiple user accounts.

      Thanks and Regards,

      Naresh Dasika

      Author's profile photo Marco Ertel
      Marco Ertel
      Blog Post Author

      Hi Naresh,

      can you explain what you mean with multiple user accounts and their limitations?

      Thanks and Kind Regards

      Author's profile photo Naresh Dasika
      Naresh Dasika

      Besides "Administrator" account, Is it possible to create user accounts for different teams?

      Author's profile photo Marco Ertel
      Marco Ertel
      Blog Post Author

      Hi Naresh,

      this is possible if you use LDAP. Read more here.

      Kind Regards
      Marco

      Author's profile photo Naresh Dasika
      Naresh Dasika

      Hello Marco,

      Where can I see the list of improvements/enhancements to know what is changed between 2.12.4 and 2.13? I don't find this in documentation. Also anywhere we can see future improvements planned in CC?

      Regards,

      Naresh Dasika

      Author's profile photo Marco Ertel
      Marco Ertel
      Blog Post Author

      Hi Naresh,

      you can see the deltas in the release notes.

      Kind Regards
      Marco

      Author's profile photo Erich Klassen
      Erich Klassen

      Hello Marco,

      Since the SAP Cloud Connector Version 2.13.we are facing a certification issue, which does not came up with the version 2.13.1.

      Can you tell me, where I can find the files for the previous release 2.13.1?
      When I try to open https://tools.hana.ondemand.com/additional/sapcc-2.13.1-windows-x64.msi we are facing a 404 Message.

      The error in the 2.13.2 is the following:

      2021-08-06 11:40:37,378 +0200#WARN#com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler#tunnel-client-5-1#0x2fe11b05#Protocol processing error: com.sap.core.connectivity.protocol.http.handlers.HttpProtocolException: Invalid server certificate
      
      2021-08-06 11:40:37,378 +0200#ERROR#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-5-1#0x2fe11b05#Write operation FAILED for payload message packet with size 732 for client channel [id: 0x51d50ce4, L:/127.0.0.1:57233 - R:myinternalhost.local/127.0.0.1:443]. Cause: io.netty.handler.ssl.SslClosedEngineException: SSLEngine closed already
      

      I also went through the release notes and couldn't find any helpful information.
      https://help.sap.com/doc/43b304f99a8145809c78f292bfc0bc58/Cloud/en-US/98bf747111574187a7c76f8ced51cfeb.html?from=2021-01-01&to=2021-08-06&sel1=Connectivity

      It would be great, if you can help here 🙂

      Beste regards,
      Erich

      Author's profile photo Christoffer Fuss
      Christoffer Fuss

      Hi Erich Klassen , I get exactly the same error after the update to 2.13.2. Do you have a solution for this?

      Best regards,

      Chris

      Author's profile photo Erich Klassen
      Erich Klassen

      Hi Chris,

      I was lucky that I have the Cloud Connector WAR file from a previous installation of version 2.13.1 on my local system.

      We removed the war file from the installed SCC verion 2.13.2 and replaced it with 2.13.1 under the webapps directory of the SCC installation. Even if we download the newest patch, just replacing the WAR did the trick for us.

      If you want I can share the war file with you. (58,9MB)

      Best regards,

      Erich

      Author's profile photo Manol Valchev
      Manol Valchev

      Hi Chris, Hi Erich,

      Have you opened support ticket(s) for this already?

      From the error, one can see that it's about the TLS connection between 127.0.0.1:57233 and myinternalhost.local/127.0.0.1:443 which is all local for the SCC host (due to both client and server being on same host).

      It would be helpful if you provide SAP with TRACE level of "Cloud Connector Loggers" from the time of reproducing the problem, also share the public data of the certificates for the TLS connection.

      Kind Regards,
      Manol

      Author's profile photo Manol Valchev
      Manol Valchev

      Hi Chris, Hi Erich,

      You may check in more details the release notes of Connectivity - Cloud Connector - Security Fixes, here's a direct link: August 12, 2021

      You may also set the "Cloud Connector Loggers" to TRACE level and "TLS trace" option in the cloud connector to observe the exact details for the error with the backend certificate, see more in Cloud Connector - Troubleshooting documentation.

      Regards,
      Manol

      Author's profile photo Karsten Köppe
      Karsten Köppe

      Hi Manol,

       

      thanks for the advice with the required logging options for the Cloud Connector.

      Due to security improvements in Version 2.13.2

      "Improper Certificate Validation

      The affected functions have been enhanced to do all the necessary validations when communicating with backends."

       

      an consumption of an https Mapping to an BE System seems to be handled stricter.

      Till version 2.13.1 it was sufficient to set the IP Adress of an BE System as an Internal Host of an https Mapping.

      From version 2.13.2 the value of Internal host is checked against the icm Parameter icm/host_name_full of the BE System.

      We changed this in our https Mappings did the update to Version 2.13.2 again and it is working perfectly fine now.

      Author's profile photo Karsten Köppe
      Karsten Köppe

      Hi Erich,

       

      the root cause in our scenario was the following:

      Peer host <IP Adress of the BE System> does not match certificate DNS names [<icm/host_name_full    of the BE System>]

      When we set up https Mappings to Backend Systems in our CloudCOnnector, we enter the IP Adress of the BE System in the Field internal Host

      We had to change the IP Adress to the Domain name.  After that it worked perfectly fine