Skip to Content
Author's profile photo Jürgen Schötteler

How to setup SAP C4C CTI-Integration using https

I want to share my “lessons learned” regarding https-configuration of CTI / Live-Activity

My knowledge is based on following sources:

Some hints regarding http

First advice:  Do the initial setup/testing using HTTP. Once this is working, switch to HTTPS.

As mentioned before, my favourite setup-how to is

Using Microsoft-Internet-Explorer, follow . In my case I also had to add localhost to trusted-sites in addition.

Using Google Chrome, is still correct. But as shown here this ends in security-warnings

This is a “no-go” from my point of view: …don’t care about this security warning, it’s safe… just ignore & continue…
(Please comment, how you think about this!)


How to switch to https

Preparations for local client

Mainly you have to follow

Unfortunately this refers to a deprecated MS-tool named makecert. The new tool is named New-SelfSignedCertificate (according to ).

Unfortunately I wasn’t able to transfer the settings to New-SelfsignedCertifacate. Solution in my case:  My IT-Webserver-colleague created a webserver-certificate for CN localhost (Thanks Daniel).

So I got a certificate stored in a .pfx-file

This has to be installed as Administrator (doubleclick) and saved to “Local computer” (not current user!).
Now you have to lookup the fingerprint of this certificate: Please start certlm.msc (as administrator) and navigate to “Own certifactes”/ certifcates, details-tab and look for the fingerprint

(sorry for “german” screenshot)

This fingerprint has to be copied to clipboard. Spaces have to be deleted, and it has to be “pure” ASCII.

In my case the fingerprint is b4a7274eb7bcd41a0536353addfd3b3c5aca3948 (your’s will be different)

Now proceed according to with following command (as administrator using cmd)
netsh http add sslcert ipport= certhash=b4a7274eb7bcd41a0536353addfd3b3c5aca3948 appid={7e46cd40-39c6-4813-b414-019ad22e55b2}

This will “connect” the certificate with the C4C-Client-Adapter.

Finally check the result: Call up URL https://localhost:36731/CTIMain.htm

It should look like this

Important is, the green lock and the word “Sicher” = “Secure”.

Everything else means, the certificate isn’t correct yet.


Check/Change C4C-Liveactivity to use https

This is hidden inside Scoping (strange, but that’s the way it is):


Test it

Now you can test this using the Simulate-button of CTI-Adapter
(I deleted browsercache to be sure)

In my case I struggled according to FAQ topic 4)

F12 – Developer-Tools & SAP-Support have been the solution in my case.


Final Result

Simulate Call works (Live activity is updated) and Webbrowser shows a “Secure” connection.



1) Currently I still struggle with a tiny “warning” regarding unsecure scripts:

(ongoing SAP-incident). Nevertheless it seems not to interfere the functionality. I’ll update this article, once this is fixed.


2) I intend to add another blog-article with details regarding Inbound-CTI-Setup using CISCO Jabber in  near future.


3) Please check also my “idea” how to improve Live-Activity


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.