Several SSL-Certificates in STRUST

[frank_lauerbach]

Hello,

I'm not sure, if this is right place for my question, but I will try it.

On one SAP WAS 7.0 we have two BSP-Applications.

Each application uses an seperate URL, for example

shopa.test.com

shopb.test.com

Access should be realized over two SAP webdispatchers.

Both applications should run with SSL.

Is it possible to install two SSL-Certificates in the STRUST?

Installing a SSL-Certificate in STRUST is not the problem, I did several times.

What happens, if there is an existing certificate, and the server-pse will be changed to create

an new CR for the second URL.

Can anybody help me or did this before?

Thank you

Frank

[Former Member]

Hi,

>Access should be realized over two SAP webdispatchers.

>

>Both applications should run with SSL.

>Is it possible to install two SSL-Certificates in the STRUST?

One possible solution is to use the web dispatchers for SSL.

Install one SSL-certificate on each Web dispatcher.

Regards,

Olivier

[frank_lauerbach]

Hello,

of course this is a possible solution.

If we want an end to end encryption, the certificates in strust are necessary.

greets

Frank

[Former Member]

Hi,

>If we want an end to end encryption, the certificates in strust are necessary.

You did not say that you wanted end to end encryption...

I don't know if what you want to do is possible.

I would experiment with virtual hosts creation at the SICF level and create 2 SSL servers entries in STRUST

Menu --> Environment --> SSL Server Identities

It adds your created entry to the main tree of STRUST and you can then create a new SSL server certificate.

Hope this helps,

Olivier

[Former Member]

Hello,

My problem is exactly the same. We could create the virtual hosts (e.g: a.domain1.local and b.domain2.local) and two different SSL Server Identity with certificate have been created as well (first for a.domain1.local and the other for b.domain2.local).

The problem is:

When client (browser) access to the first site:

To a.domain1.local then WEB AS provide the correct SSL cert (a.domain1.local which called "standard" Server PSE in STRUST)

But when I access to the second site via browser (b.domain2.local) then the SSL cert remain the same: a.domain1.local so it seems the second SSL identity could not be reached from WEB AS.

Any ideas?

Thanks in advance,

Peter

[Former Member]

Hi,

Sorry, no ideas.

I used the 2 web dispatchers trick which works perfectly for my need.

Regards,

Olivier