Forum Discussion

lindi2k3's avatar
lindi2k3
Occasional Visitor
16 days ago

SSL Keystore Request Property not working since 3.6.2

Hello Community,

up until updating to Version 3.6.2/3.6.3 i had no complications using the request property for SOAP requests "SSL Keystore". I used it either via environment properties or with the explizit configured keystore name

f.e. 

 

 

 

When downgrading to 3.6.1 the client authentification works fine. With 3.6.2 and 3.6.3 ReadyAPI is not sending any client auth information to the server.

So here is my question. What changed? Am i missing a new property or configuration i did not find in the update history?

 

Best regards

SOAP

2 Replies

  • davinci020's avatar
    davinci020
    Occasional Contributor
    9 days ago

    I'm having exact the same problem and downgraded back to version 3.61.0.
    Already made a ticket at the servicedesk like weeks ago, but still no solution.

    Ticket eventually got closed because I couldn't send them my reproduction-video (because file was too large for email). 

    Meanwhile 3.63.0 still same problem occurs and my whole team is stuck with 3.61.0.

  • CarlosValcarcel's avatar
    CarlosValcarcel
    Icon for Staff rankStaff
    10 days ago

    Hmm.
    My recommendation would be threefold:

    • Downgrade to 3.6.1 (which you say works) until the issue is resolved.
    • (Please) Log a bug / create a Support Case with SmartBear: Provide them with a small project/test case that uses SSL Keystore and fails in 3.6.2/3.6.3, works in 3.6.1.
    • As a workaround, you can define the client certificate keystore globally under Preferences → SSL (KeyStore / password) and remove the request-level SSL Keystore override—i.e., rely on the global setting. That might bypass whatever changed.

    Let me know if that helps!