SSL cert renewal in Portal

[Former Member]

Hi,

We have renew the SSL certificate in the Portal.

After logging onto the Visual admin with administrator, when I open the views from key storage.

I have create the SSL key  using the TrustedCAs and generate the CSR and send it to CA to sign.

Now my question is, is there any difference in which view I use to generate the key.

Should i have to use service_ssl in key storage?

Will that make the difference?

And store certificate is mandatory check box?

Thanks,

AP

[Former Member]

Thanks James!

In the Following scenario where Apache acts as a reverse proxy where the key pair is stored

.

Portal app running in JAVA stack

^

|              HTTPS

v

Apache

^

|              HTTP

v

Web app running in JAVA stack

    Apache needs to have the private key + certificate installed.               (As above)

    The JAVA stack is in HTTPS client mode so needs to have the certificate (but not private

key) installed in it’s trusted (root) certificate list.

I have created a key pair in Java stack and saved the private key in .key format. Send the

CSR  to CA and get the signed certificate back from CA.

Then I imported into service_ssl view by selecting the private key entry.

I took the private key and signed certificate(public key) to Apache conf folder.

Restarted the service of Apache

Now I don't need the private key in Java stack, I only need the public key here as it works

as a Client and will send HTTPS request to Apache.

My question,Can I just delete the private key in the service_ssl view after importing CSR

response file. And reload the Response file into that view?

If Yes, then what was the point of importing CSR response here? What does it do when I imported the CSR response file that it changes the IsserDN to CA's and it's corresponding validity.

Thanks,

AP

[James_Connolly]

Hi,

For ssl you should use the service_ssl in key storage.

Also the store certificate check box is so a certificate gets generated.

Please see the following documentation:

http://scn.sap.com/docs/DOC-12546

regards,

James