Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

Out of the box, the HANA Cloud Connector (SCC) is not secure, as clearly documented by the General Security Status:

Therefore, in this blog series, I will show how to secure your SCC with OpenSSL certificates item by item, until the General Security Status is all green.

In my pervious blog series, I showed how to setup a Certification Authority with OpenSSL and with this to securely single-sign-on to your Fiori Launchpad. In this blog, I start with the SCC UI Certificate, leveraging the results from the above blogs.

As mentioned in the General Security Status, the out of the box SSL certificate does not use the host name as its common name (CN) and is therefore not trusted:

It is still possible to work with the SCC in this state via a browser security exception, but I will show how to properly secure the connection.

First I crate a Certificate Signing Request (CSR) with the correct hostname as CN:

And save it as a file:

I then import this file into TinyCA:

And check that the details are correct:

Next, I sign the request:

And export the resulting certificate to file:

After importing it into my SCC:

I restart my SCC and the connection becomes secure:

Given that my CA certificate had already been imported into my browser:

And of course I also get my green light for the UI Certificate in the General Security Status:

In my next blog of this series I will show how to install a SCC trusted System Certificate, put your CA certificate in the Trust Store, install a SCC CA Certificate and with that enable Principal Propagation.

Labels in this area