Service Virtualization

 View Only
  • 1.  Unable to record the txns for apigateway

    Posted Oct 02, 2019 04:27 PM
    I want to virtualize https call via a recording but not getting any txns on recorder.
    Its an apigateway and calls are https. I used host name (qa-apigateway.delta.com) and did SSL to server check box checked and didn't get any txns while hitting to url.

    But same live url works in Postman without using any certificate. Not sure what I'm missing here. Earlier I recorded some of the https soa callls and they were successful.

    Please help.


  • 2.  RE: Unable to record the txns for apigateway

    Broadcom Employee
    Posted Oct 03, 2019 02:34 AM
    Hi Ritu
              Can you share your recorder screenshot, the page where you fill in the proxy/target ports and SSL settings. Please black out any sensitive info.

    regards
    Sankar

    ------------------------------
    Sankar Natarajan
    Service Virtualization Product Engineering Team
    Broadcom
    ------------------------------



  • 3.  RE: Unable to record the txns for apigateway
    Best Answer

    Posted Oct 03, 2019 02:59 AM

    Hi Ritu,

     

    Shiney (Broadcom Support) solved a very similar issue for me earlier this week.

     

    Turn on HTTP/SSL DEBUG in your workstation (via Help Menu). You might see an SSL-handshake error during recording.

     

    Specifically, if you see an alert on the TLS version, something like:

    28] Filter thread for 832834.dxi-na1.saas.broadcom.com:443->127.0.0.1:52307, SEND TLSv1.2 ALERT: fatal, description = handshake_failure

     

    Than you can activate the TLSV properties in your local.properties file.

    Add:  

    https.protocols= TLSv1.2,TLSv1.1,TLSv1    in local.properties 

    Restart Workstation and see if this helps.

     

    Cheers,

    Danny

     

    ::DISCLAIMER::

    The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.






  • 4.  RE: Unable to record the txns for apigateway

    Posted Oct 03, 2019 02:27 PM
    Hi Danny- This is the perfect solution and it worked. Thanks much for your help!

    Regards,
    Ritu


  • 5.  RE: Unable to record the txns for apigateway

    Posted Oct 04, 2019 03:51 AM

    I was just a conduit, all credit goes to Shiney.

     

    Cheers,

    Danny

     

    ::DISCLAIMER::

    The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.