- SAP Managed Tags:
As you know, the SAP Cloud Connector (CC) lets you securely connect your on-premises systems with the SAP Cloud Platform. You can install it on Windows, Linux and Mac.
To run the CC, you need a java installation. I am using the SAP JVM 8.1 (that you can download here, by-the-way: https://tools.hana.ondemand.com/#cloud)
As a Mac user, I recently upgraded to Catalina. I had a couple of issues to begin with, but nothing special. But when I tried to start my CC lately, I came up with a lot of security warnings.
Here is an example of that warning:
"“libdt_socket.dylib” cannot be opened because the developer cannot be verified."
Usually, you deal with them here by trusting the program in your security settings. Here is an example:
But allowing the execution one-by-one as the CC was starting did not help. There were still permissions missing.
As a non-security expert, I found the following workaround: I ended up opening my Finder and giving "read & write" access rights on my JVM folder to "everyone".
After that, I could allow the execution of java and the associated libraries, and eventually start the CC.
Reverting the access rights to "everyone" to "read only" still allows to start my CC.
Again: I am no security expert so there may be better solutions to this. But hopefully this "quick and dirty" solution will help someone else!
To run the CC, you need a java installation. I am using the SAP JVM 8.1 (that you can download here, by-the-way: https://tools.hana.ondemand.com/#cloud)
As a Mac user, I recently upgraded to Catalina. I had a couple of issues to begin with, but nothing special. But when I tried to start my CC lately, I came up with a lot of security warnings.
Here is an example of that warning:
"“libdt_socket.dylib” cannot be opened because the developer cannot be verified."
Usually, you deal with them here by trusting the program in your security settings. Here is an example:
But allowing the execution one-by-one as the CC was starting did not help. There were still permissions missing.
As a non-security expert, I found the following workaround: I ended up opening my Finder and giving "read & write" access rights on my JVM folder to "everyone".
After that, I could allow the execution of java and the associated libraries, and eventually start the CC.
Reverting the access rights to "everyone" to "read only" still allows to start my CC.
Again: I am no security expert so there may be better solutions to this. But hopefully this "quick and dirty" solution will help someone else!
6 Comments
