How to solve SSL exception during Rest secure service test

[Shivam.garg]

Hello All,

 

I am again facing issue during testing REST secure api. I enabled SSL/HTTP trace and able to see below info. I have provided cert details in local.properties file + have changed in LisaWorkstation.vmoption file with this -Dhttps.protocols=TLSv1, SSLv2 + I have tried changing in java.security file as well.

 

But still it is not passing and throwing below exception.

 

[ 1] [SSL Handshake Summary]

[ 1] [SSL Handshake Summary] RECV TLSv1 ALERT: fatal, handshake_failure

[ 1] [SSL Handshake Summary] javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

[ 1] [SSL Handshake Summary] See Alert or Exception for details

 

 

I checked with message broker team and they are saying this protocol is configured at their side. I have tried every thing in Lisa what I am aware  but not working. So please let me know any thing else I can do.

 

mqsireportproperties BDSMBRB1 -e ENQ-IIB-RestGateway -o HTTPSConnector -r
sslProtocol='SSL_TLSv2'
mqsireportproperties BDSMBRB2 -e ENQ-IIB-RestGateway -o HTTPSConnector -r
sslProtocol='SSL_TLSv2'
mqsireportproperties BDSMBRB1 -e FPS-IIB-RestGateway -o HTTPSConnector -r
sslProtocol='SSL_TLSv2'
mqsireportproperties BDSMBRB2 -e FPS-IIB-RestGateway -o HTTPSConnector -r
sslProtocol='SSL_TLSv2'

[Legacy User]

You included the following in your post:

mqsireportproperties BDSMBRB1 -e ENQ-IIB-RestGateway -o HTTPSConnector -r sslProtocol='SSL_TLSv2'

 

Does this mean, the expectation is that DevTest must use TLSv2 or TLSv1.2?  

The setting you applied only enabled TLSv1. To set TLSv1.2, use this property in local.properties:  https.protocols=TLSv1.2,TLSv1.1,TLSv1

 

If TLSv2 is expected, you may need to contact CA Support as I do not believe TLSv2 is supported as of DT v10.1.

[Shivam.garg]

As per MB team, if it is TLS only then it  is fine. But here one strange scenario is there, we have two REST APIs , one is working fine and one is throwing exception while both MB flows have identical set up regarding protocols.

 

I think I have to raise support case to check this as it is impacting failover testing.

 

any other suggestion from your side, please?

 

Cheers..

[Legacy User]

Since you have a working example and the other service is not replicating the same behavior, your approach to open a ticket is the correct thing to do.  After resolution, update this post so others can use the knowledge gained about the resolution.