Skip to Content
avatar image
Former Member

Certificate error for CMC and Launchpad


I built a new BO environment,i have configured SSL on tomcat by modifying server.xml.

Now my cmc page is giving me a certificate error.(https://servername:8443/BOE/CMC)

I have the keystore file,i need ca.cer and .csr .May i know how to configure these files with BOE.

Any KBA or Notes will be helpful.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Aug 17, 2017 at 05:29 PM

    Your certificate error has nothing to do with BO. It is because if you used self signed certificate browsers do not trust them.
    You can make a browser trust your certificate - there are plenty of how to's on the internet.
    General information on tomcat and ssl is here

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 10, 2018 at 07:04 PM

    Hello Denis Konovalov,

    We need your expert advise, we are seeing same issue while configuring SSL authentication for BOBJ in our landscape. we are not using Self signed certificates, we have our Own CA Autherity they have provided us the Signed Certificates. please have a look at the below process which we have followed in short.

    1) Generated .keystore by using - Keytool

    2) Generated Certificate request (Csrname.p10) , .key and phassphrase.txt files and shared Csr request with CA Authorities and they have provided us the signed certificates such as Root certificate (CA Certificate), Server certificate and intermediate certificate.

    3) we have generated the .PSE by using above mentioned certificates, so now that we have got all files to go ahead with the configuration for tomcat and SIA

    4) we have updated the tomcat Server.xml file with Keystore details and 8443 port.

    5) We have imported CA and Server Certificates into .Keystore file by using Keytool import command and i have validated the .Keystore file as well its showing 4 certificates inside the .Keystore file

    6) maintained all the details in tomcat Java & Enabled SSL in SIA along with all certificates. Restarted tomcat and SIA ( am not seeing any issues for both restarts)

    6) We are successfully able to connect to https://servername:8443/ but it's showing certificate authority issues.

    So we have red admin guides , OSS notes and other blogs, i know we are not using Self signed certificate methodology but falling in to the situation exactly like Self signed certificates, since my browser complaining about certificate issues which should happen only with Self signed certificate scenario, we are Sapgenpse to generate all the certs and we dont want to use self signed certificate strategy as we have our own CA to provided the Signed Certificates.

    We are working with SAP as well with high priority message but we are not able to resolve this issues. am requesting you to provide your expert advise, if you have seen such type of issues.


    Srinivas Korva

    Add comment
    10|10000 characters needed characters exceeded