Skip to Content

Issue configuring SSL on WACS


With the recent upgrade of our platform towards 4.2 SP3 we have faced the need of enabling HTTPS on WACS in order to fix the issue when using Bi Admin Cockpit when using https well described on KBA (2277129 - Unable to access BI Administrators' Cockpit using https in BI 4.2)

We have followed in detail all the steps describe on above mentioned KBA and particularly how to enable WACS HTTPS by checking content described on following notes:

- 2381285 - WACS 'Running with Errors' following HTTPS configuration - BI 4.x

- 1618311 - How to configure Secure Socket Layer (SSL) on Web application Container Server (WACS) using JKS (Java Key Store) as certificate type

In our case we have decided to create a JKS as certification type.

After restarting WACS HTTPS appears properly on the list of running WACS connectors

but when check the following URL


following issues appears:

Chrome: Error message: ERR_SSL_VERSION_OR_CIPHER_MISMATCH. The client and server don't support a common SSL protocol version or cipher suite.

IE: There is a problem with this website’s security certificate.

I assume that the problem must arise from java key store file I created but I am a bit lost about. I am not a certificate expert and I strictly followed same steps detailed on KBA 1618311 to generate it.

So, what is going wrong here?

Thanks in advance for your help,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Apr 21, 2017 at 06:52 PM
    Add comment
    10|10000 characters needed characters exceeded

  • Oct 19, 2017 at 01:06 PM

    I had the same problem on BI 4.2 SP4 PL2. The problem was basically that the Java keytool generates keystores with 1024 default size. SAP BI4.2 SP4 only accepts minimum keysize 2048. So you have to manually define your keysize. Afterwards BI-Administrators Cockpit was working.

    See here for more details.


    Add comment
    10|10000 characters needed characters exceeded

  • Apr 30 at 11:30 AM

    Download Keystore explorer and open the WACS.jks in it.

    Check the keystore size, it should be 2048.

    Add comment
    10|10000 characters needed characters exceeded