Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    5
  • Subscribers subscribers
    17
  • Views views
    534
  • Users 0 members are here
Related
Options

Windows Socket Protocol - SSL Required so using lrs_start_ssl - How Can I Add The Correct Certificate to this Request

Cameron Jones

Hi all,

We are using the Windows Socket Protocol to script an interface that requires SSL we have found the lrs_start_ssl function that allows to do the SSL Handshake however it is not completing that handshake successfully and we are getting the below error - 

SSL error code: 1, result code -1
SSL: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate
Error : Function execution failed. Error code : 9001.

Talking with the engineers for the System Under Test they say that we are not presenting a certificate - so my question is how do I add a certificate to this request or control which certificate is used by this request?

We are using Virtual User Generator Version 2022 build 433

Parents
  • 0  

    This error indicates that a client certificate is required in this handshake.

    I suggest to capture a wireshark log for your network connection (without vugen recording) and check if a certificate is required or not (sslkey may be required to deprecate the data); you can also capture the network data for vugen recording and do a comparison to see what is missed in your script.

  • 0 in reply to   

    Hi     would need you help.

    I'm getting same error where I need to Test an rest API below are the observation

    1. By Adding Client certificate (certificate file) and disabling/turning off SSL certification verification in postman request works fine.

    2. When I run the script from Vugen I'm getting below error

     Error -27774: SSL protocol error when attempting to connect with host "hostname" [MsgId: MERR-27774]
    Action.c(42): Error -27760: Request

    ssl_handle_status encounter error : SSL_ERROR_SSL, error message : error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure.

    Tried using different SSL version  (TLS1.2, TLS1.3, 3, 2&3): web_set_sockets_option("SSL_VERSION", "TLS1.2");  know handshake is failing but same thing works in postman.

Reply
  • 0 in reply to   

    Hi     would need you help.

    I'm getting same error where I need to Test an rest API below are the observation

    1. By Adding Client certificate (certificate file) and disabling/turning off SSL certification verification in postman request works fine.

    2. When I run the script from Vugen I'm getting below error

     Error -27774: SSL protocol error when attempting to connect with host "hostname" [MsgId: MERR-27774]
    Action.c(42): Error -27760: Request

    ssl_handle_status encounter error : SSL_ERROR_SSL, error message : error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure.

    Tried using different SSL version  (TLS1.2, TLS1.3, 3, 2&3): web_set_sockets_option("SSL_VERSION", "TLS1.2");  know handshake is failing but same thing works in postman.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.