13 years ago
soapUI doesn't read certificate entries from keystores
In the following example:
When adding the keystores, the status for keystore.jceks isn't OK:

There is another side-effect that tends to prove that soapUI only reads key entries:
When configure an outgoing WS-Security Encryption, and selecting a keystore that doesn't contain any key entry, the "alias" combo doesn't contain any item.
One could normally select the alias corresponding to the certificate/public key to be used to encrypt.

When select keystore.p12, the alias corresponding to the key entry is diplayed in the combo.
When selecting keystore.jceks to check signatures of in-going messages, signature checking fails while processing the server response.
This is really surprising, as you can't base any security system on private key exchanges!!
Please advise.
Thanks.
- keystore.p12 contains only one entry, which is a "Key Entry"
- keystore.jceks contains only one entry, which is a "Certificate Entry"
When adding the keystores, the status for keystore.jceks isn't OK:

There is another side-effect that tends to prove that soapUI only reads key entries:
When configure an outgoing WS-Security Encryption, and selecting a keystore that doesn't contain any key entry, the "alias" combo doesn't contain any item.
One could normally select the alias corresponding to the certificate/public key to be used to encrypt.

When select keystore.p12, the alias corresponding to the key entry is diplayed in the combo.
When selecting keystore.jceks to check signatures of in-going messages, signature checking fails while processing the server response.
This is really surprising, as you can't base any security system on private key exchanges!!
Please advise.
Thanks.