Service Virtualization

Expand all | Collapse all

javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

kasina

kasinaApr 19, 2018 10:36 AM

  • 1.  javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 10, 2018 07:14 AM

    I'm trying REST service  using VSE version 1.1.0 but getting below issue. 

    Can someone guide me with the steps to fix this issue?

     

    Version:1.0 StartHTML:0000000128 EndHTML:0000002692 StartFragment:0000000140 EndFragment:0000002678 SourceURL:about:blank ============================================================================ | HTTP ============================================================================ | Message: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure ---------------------------------------------------------------------------- | Trapped Exception: Received fatal alert: handshake_failure | Trapped Message: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure ---------------------------------------------------------------------------- STACK TRACE javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.Alerts.getSSLException(Alerts.java:154) at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) at com.itko.lisa.test.CommTrans.doSend(CommTrans.java:1074) at com.itko.lisa.test.CommTrans.send(CommTrans.java:843) at com.itko.lisa.test.CommTrans.sendGET(CommTrans.java:767) at com.itko.lisa.ws.rest.RESTNode.doSend(RESTNode.java:221) at com.itko.lisa.ws.rest.RESTNode.doWebTrans(RESTNode.java:171) at com.itko.lisa.ws.rest.RESTNodeBase.execute(RESTNodeBase.java:380) at com.itko.lisa.ws.rest.RESTNodeEditor.lambda$executeRequest$7(RESTNodeEditor.java:1072) at java.lang.Thread.run(Thread.java:745) ============================================================================



  • 2.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 11, 2018 10:59 AM

    I have enabled SSL/HTTP debug and found below exception.

    In Local.properties put 'https.protocols=SSLv3,TLSv1.2,TLSv1.1"

     

    Could you please help me out on the issue.

     

     

    [ 5] ***
    [ 5] found key for : lisa
    [ 5] chain [0] = [
    [ 5] [
    [ 5] Version: V3
    [ 5] Subject: CN=Lisa, OU=Lisa, O=Lisa, L=Dallas, ST=Texas, C=US, EMAILADDRESS=support@itko.com
    [ 5] Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
    [ 5]
    [ 5] Key: Sun RSA public key, 1024 bits
    [ 5] modulus: 107577342571485428802393728049184265786056348388364405824138117397977455761833138845329880593678805610027793821217939298848284286683543926634250841496293888229172692948746730869670908754188073542091973621265074265583182385560072567366227383567380577316296862528343858318946945517967854106447414857653511333997
    [ 5] public exponent: 65537
    [ 5] Validity: [From: Fri Aug 20 21:37:30 IST 2010,
    [ 5] To: Tue Jan 05 21:37:30 IST 2038]
    [ 5] Issuer: CN=Lisa, OU=Lisa, O=Lisa, L=Dallas, ST=Texas, C=US, EMAILADDRESS=support@itko.com
    [ 5] SerialNumber: [ 4c6ea842]
    [ 5]
    [ 5] ]
    [ 5] Algorithm: [SHA1withRSA]
    [ 5] Signature:
    [ 5] 0000: 2B 7F 77 08 DE 2F 74 E3 CD 0F 58 D8 57 D9 08 2E +.w../t...X.W...
    [ 5] 0010: AC 57 A7 02 81 07 B7 F8 5B 68 AE 22 22 C6 75 EE .W......[h."".u.
    [ 5] 0020: C2 41 B6 23 DE ED 17 F8 21 AE 3B ED B6 EA 1A 17 .A.#....!.;.....
    [ 5] 0030: A4 5F 95 FD BE AE 74 DA 75 64 19 D6 60 0A 63 61 ._....t.ud..`.ca
    [ 5] 0040: B6 2A E1 FB 06 C5 36 E5 00 0C EB 20 EF FA 82 29 .*....6.... ...)
    [ 5] 0050: 40 39 EA 61 3A 27 CF 4F 00 18 33 E8 31 4C E4 C5 @9.a:'.O..3.1L..
    [ 5] 0060: 44 98 60 15 80 FE 85 FB BF BD 95 AB 35 14 F7 16 D.`.........5...
    [ 5] 0070: 9D 58 F5 26 10 B7 76 7D 43 20 A7 4B F4 ED EE CF .X.&..v.C .K....
    [ 5]
    [ 5] ]
    [ 5] ***
    [ 5] X509KeyManager passed to SSLContext.init(): need an X509ExtendedKeyManager for SSLEngine use
    [ 5] trigger seeding of SecureRandom
    [ 5] done seeding SecureRandom
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_anon_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
    [ 5] Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
    [ 5] Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    [ 5] Ignoring unavailable cipher suite: TLS_DH_anon_WITH_AES_256_GCM_SHA384
    [ 5] Execute REST Node, setSoTimeout(180000) called
    [ 5] Allow unsafe renegotiation: false
    [ 5] Allow legacy hello messages: true
    [ 5] Is initial handshake: true
    [ 5] Is secure renegotiation: false
    [ 5] Ignoring disabled protocol: SSLv3
    [ 5] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 for TLSv1
    [ 5] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_DH_anon_WITH_AES_128_GCM_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_DH_anon_WITH_AES_128_CBC_SHA256
    [ 5] Ignoring unsupported cipher suite: TLS_RSA_WITH_NULL_SHA256
    [ 5] %% No cached client session
    [ 5] *** ClientHello, TLSv1
    [ 5] RandomCookie: GMT: 1506681132 bytes = { 211, 64, 179, 124, 177, 128, 143, 20, 220, 151, 79, 109, 14, 128, 43, 128, 151, 172, 47, 82, 197, 118, 25, 233, 41, 199, 147, 48 }
    [ 5] Session ID: {}
    [ 5] Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV, TLS_ECDH_anon_WITH_AES_128_CBC_SHA, TLS_DH_anon_WITH_AES_128_CBC_SHA, TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA, SSL_DH_anon_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_DH_anon_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA, TLS_ECDHE_ECDSA_WITH_NULL_SHA, TLS_ECDHE_RSA_WITH_NULL_SHA, SSL_RSA_WITH_NULL_SHA, TLS_ECDH_ECDSA_WITH_NULL_SHA, TLS_ECDH_RSA_WITH_NULL_SHA, TLS_ECDH_anon_WITH_NULL_SHA, SSL_RSA_WITH_NULL_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA, TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5]
    [ 5] Compression Methods: { 0 }
    [ 5] Extension elliptic_curves, curve names: {secp256r1, sect163k1, sect163r2, secp192r1, secp224r1, sect233k1, sect233r1, sect283k1, sect283r1, secp384r1, sect409k1, sect409r1, secp521r1, sect571k1, sect571r1, secp160k1, secp160r1, secp160r2, sect163r1, secp192k1, sect193r1, sect193r2, secp224k1, sect239k1, secp256k1}
    [ 5] Extension ec_point_formats, formats: [uncompressed]
    [ 5] ***
    [ 5] Execute REST Node, WRITE: TLSv1 Handshake, length = 187
    [ 5] Execute REST Node, WRITE: SSLv2 client hello message, length = 179
    [ 5] Execute REST Node, READ: TLSv1 Alert, length = 2
    [ 5] Execute REST Node, RECV TLSv1.2 ALERT: fatal, handshake_failure
    [ 5] Execute REST Node, called closeSocket()
    [ 5] Execute REST Node, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    [ 5] Execute REST Node, called close()
    [ 5] Execute REST Node, called closeInternal(true)
    [ 5] [SSL Handshake Summary] Thread [Execute REST Node]
    [ 5] [SSL Handshake Summary] Can not be sure if Client or Server
    [ 5] [SSL Handshake Summary] *†‡ indicates linked optional steps
    [ 5] [SSL Handshake Summary]
    [ 5] [SSL Handshake Summary] 1 RUN Client Hello -->
    [ 5] [SSL Handshake Summary] 2 UNKNOWN <-- Server Hello
    [ 5] [SSL Handshake Summary] 3* UNKNOWN <-- Server Certificate (Public Key)
    [ 5] [SSL Handshake Summary] 4† UNKNOWN <-- Request Client Certificate
    [ 5] [SSL Handshake Summary] 5* UNKNOWN Verify and Trust Server Certificate v
    [ 5] [SSL Handshake Summary] 6‡ UNKNOWN <-- Server Key Exchange
    [ 5] [SSL Handshake Summary] 7 UNKNOWN <-- Server Hello Done
    [ 5] [SSL Handshake Summary] 8† UNKNOWN Client Certificate (Public Key) -->
    [ 5] [SSL Handshake Summary] 9† UNKNOWN v Verify and Trust Client Certificate
    [ 5] [SSL Handshake Summary] 10 UNKNOWN Client Key Exchange -->
    [ 5] [SSL Handshake Summary] 11† UNKNOWN Certificate Verify Confirmation -->
    [ 5] [SSL Handshake Summary] 12 UNKNOWN Client Change Cipher Spec -->
    [ 5] [SSL Handshake Summary] 13 UNKNOWN Client Finished -->
    [ 5] [SSL Handshake Summary] 14 UNKNOWN <-- Server Change Cipher Spec
    [ 5] [SSL Handshake Summary] 15 UNKNOWN <-- Server Finished
    [ 5] [SSL Handshake Summary]
    [ 5] [SSL Handshake Summary] RECV TLSv1.2 ALERT: fatal, handshake_failure
    [ 5] [SSL Handshake Summary] javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    [ 5] [SSL Handshake Summary] See Alert or Exception for details


  • 3.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    Best Answer

    Posted Apr 16, 2018 01:59 PM

    What combinations of protocols does your web server support?

     

    By default we try to maintain the most compatible set, being TLSv1,SSLv3,SSLv2Hello, but some newer servers may require newer versions.

     

    It looks like you are trying to hit a TLSv1.2 web server with a combination of TLSv1 and SSLv2 Client Hello (which is usually not allowed).

     

    You can try limiting the client to TLS1.2 using 

     

    https.protocols=TLSv1.2

     

    in your local.properties file.



  • 4.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 17, 2018 10:02 AM

    Hi Brian,

    thanks for your support,

     

    My browser supporting protocols below on image.

     

     

    I have tried using protocol 

    https.protocols=TLSv1.2

     

    Facing exception:

    [ 1] ***
    [ 1] Execute REST Node, WRITE: TLSv1 Handshake, length = 187
    [ 1] Execute REST Node, WRITE: SSLv2 client hello message, length = 179
    [ 1] Execute REST Node, READ: TLSv1 Alert, length = 2
    [ 1] Execute REST Node, RECV TLSv1.2 ALERT: fatal, handshake_failure
    [ 1] Execute REST Node, called closeSocket()
    [ 1] Execute REST Node, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    [ 1] Execute REST Node, called close()



  • 5.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 17, 2018 10:04 AM
    Hi Brian,
    I am new into this tool, currently we are using SOAP UI but we are plaining to move CA LISA.
    Before moving to the tool my client asked one presentation on tool LISA Service virtualization.
    Recently downloaded Trial free version " CA SV community edition 1.1.0(10.3.0.107)"
     
    Note:
     
    Recently my colleague told me that I have to get server certification from Dev/Admin to access the tool.
     
    1. is there any certification to access trial free version? because facing below exception.
    2. or I am using correct version? because I am not able to access Virtual Service it asking for username and password
    3. not able to access HTTPS protocol throws below exception
     
    Exception Facing in HTTP/SSL Debug:
     
    [ 1] Execute REST Node, WRITE: TLSv1 Handshake, length = 187
    [ 1] Execute REST Node, WRITE: SSLv2 client hello message, length = 179
    [ 1] Execute REST Node, READ: TLSv1 Alert, length = 2
    [ 1] Execute REST Node, RECV TLSv1.2 ALERT: fatal, handshake_failure
    [ 1] Execute REST Node, called closeSocket()
    [ 1] Execute REST Node, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    [ 1] Execute REST Node, called close()
    Please find attached image for more information.
    Kindly help me out on this issue, it will helpful for me to improve the tool


  • 6.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 17, 2018 01:05 PM

    So based on the HTTP/SSL Debug, the property change has not taken effect. How did you apply the https.protocols=TLSv1.2 property? Can you attach your local.properties file?

     

    Also, SV CE is a very lightweight, basic functionality tool to get you familiar with the basics of Service Virtualization. The full enterprise product had much more functionality. Was your colleague referring to getting credentials to access/use your enterprise deployment of Service Virtualization?



  • 7.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 18, 2018 05:33 AM

    Hi Brian,

    Yes, I am trying to access basics of service virtualisation. but I am  not able to access basic functionality on this tool.

    I thought my colleague told me about enterprise product and credentials.

     

    Kindly help me to access basic functionality because have to show demo to my client then only they will refer enterprise product.

     

     I am not able to upload my properties file so made as image file.



  • 8.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 18, 2018 05:36 AM
      |   view attached

    Hi Brian,

     

    Please find below my attached local properties file.

    Attachment(s)

    zip
    _local.properties.zip   4 KB 1 version


  • 9.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 18, 2018 09:43 AM

    You are modifying the file template (_local.properties) - you need to rename it local.properties for it to be loaded (remove the underscore).



  • 10.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 19, 2018 09:57 AM
      |   view attached

    Hi Brian,

     

    I couldn't modify the file name by default generated after deployment.  now I have modified and executed.

    Facing exception below:

    Enable : SSL/Debug.

     

    [ 1] Execute REST Node, WRITE: TLSv1.2 Handshake, length = 223
    [ 1] Execute REST Node, READ: TLSv1 Alert, length = 2
    [ 1] Execute REST Node, RECV TLSv1.2 ALERT: fatal, handshake_failure
    [ 1] Execute REST Node, called closeSocket()
    [ 1] Execute REST Node, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    [ 1] Execute REST Node, called close()

     

     

    find attached image.

    Attachment(s)

    zip
    local.properties.zip   4 KB 1 version


  • 11.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 19, 2018 10:26 AM

    Can you tell us what service you are trying to access? Is this something public that I'd be able to try?

     

    How have you been successful accessing it? In a browser or other tool?



  • 12.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 19, 2018 10:35 AM

    Hi Brian,

     

    Tried in SOAP UI.

    Method : Get

    Used url :https://jsonplaceholder.typicode.com/posts

    yes it public and you can access any browser

     

     



  • 13.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 19, 2018 10:36 AM

    Hi Brian,

     

    Please find attached image



  • 14.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 19, 2018 11:45 AM

    So the site in question is using a newer cipher than the JRE we ship supports. You can either use the http version of your request http://jsonplaceholder.typicode.com/posts or you can update the JRE used by SV CE (You can copy it over the jre directory from SoapUI as a simple means).



  • 15.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 19, 2018 12:20 PM

    Hi Brian,

    I will try and update you,

    Facing another issue .

    Can you guild to connect CA service Virtualization for create virtual service(for me virtual service is disable), not able to create virtual service

    throws below exception.

     

     

     



  • 16.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure



  • 17.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 20, 2018 07:57 AM

    Hi Brian,

     

    Little clarification.

    1.Is it version "CA SV community edition 1.1.0(10.3.0.107)" won't support assertion, database, JDBC, Filter, Properties and property transfer ?

     

    Kindly help me to understand,

    If this version not having those option then which version I can refer to buy.



  • 18.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 20, 2018 01:49 PM


  • 19.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 23, 2018 04:48 AM

    Based on your question for clarification, I struggle to understand what you are looking for. For which use cases do you need clarification on 'assertion, database, JDBC, Filter, Properties and property transfer'? It would be very helpful to understand what you want to demonstrate to your colleague.

     

    You have several options to learn about the capabilities of CA Service Virtualization. As you know, CA SV Community Edition supports a subset of features available in CA SV Enterprise Edition. If you want to learn about the basics in CA Service Virtualization please try and walk through the tutorials available in CA SV Community Edition Homepage at Tutorial for CA SV Community Edition. If you want to take a glance at the CA SV Enterprise Edition and have a guided walk through a few basic use cases using the product's Web UI, you may want to sign up for a 15-day product trial at CA Service Virtualization and Application Test TrialProduct Documentation of CA Service Virtualization gives you a lot of insights into the product's extended capabilities. If you do not have access to CA SV Enterprise Edition, but want a discussion and a demo of the full capabilities of CA SV Enterprise Edition and how it can be leveraged in your Test environments you may consider to contact a CA sales representative. If you do have access to a CA SV Enterprise Edition installation - as it sounds by one of your previous posts - you can walk through the tutorials outlined in CA Service Virtualization Tutorials, once you have been granted access. 

     

    You can use CA SV Community Edition standalone or with CA SV Enterprise Edition. If you want to use CA SV Community Edition with CA SV Enterprise Edition, you need credentials to access the Enterprise Edition's Registry service. Additionally, if your company security policy requires it, you may need a certificate for your client system to be able to connect to the Registry's server system. In order to understand how CA SV Community Edition works, I strongly recommend to walk through the accompanying tutorials mentioned above first.

     

    Hope that helps.



  • 20.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 24, 2018 04:46 AM

    Hi Ulrich,

    I am trying to get 15-days trial product 'CA Service Virtualization and Application Test" for that i have sent mail to sales team but haven't get replay.

     

    Can you provide mail id and telephone numbers?

    or if you have any other options kindly guide me.



  • 21.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 24, 2018 05:01 AM

    Did you fill out the request form at this link 15-days CA Service Virtualization Test Drive and submit it?



  • 22.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 25, 2018 12:08 AM

    Thanks lot.



  • 23.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 26, 2018 11:28 AM

    Hi Ulrich,

     

    Kindly guild me create RR file for below is my request and response.

    I failed to create proper format.

     

    Request URL: http://107.23.187.184:2001/api/admin/login
    Request Method: POST
    Request body:
    {"name": "oddzsquad", "password": "planemoney33!"}
    Response body:
    {
        "status" : true,
        "message" : "success",
        "data" : {
            "_id" : "5ad4390f65070f22f72671c6",
            "updatedAt" : "2018-04-26T15:16:09.267Z",
            "createdAt" : "2018-04-16T05:47:59.662Z",
            "name" : "oddzsquad",
            "email" : "oddzapp2017@gmail.com",
            "__v" : 0,
            "badgeCount" : 0,
            },
     
    Kindly help me to download for sample file to understand the request and response.
    example in image


  • 24.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 26, 2018 01:22 PM
    Kindly guide from to download for sample RR file DevTest solution to understand the request and response format.
    example in image


  • 25.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 26, 2018 02:59 PM

    If you have successfully requested a SV Test Drive instance, you can download a zip file of RR pairs from the landing page. Executing 'Qualify/Create Virtual Service from Request/Response Pairs' will also guide you to download this zip file. 

    SV Test Drive Screenshot

    Product documentation at Request/Response Pairs explains how to create RR pairs. It refers to locations of RR pair example files, available on a DevTest installation. For your convenience, I have attached those files to this thread.

    Attachment(s)

    zip
    Bankv5-rrpair.zip   3 KB 1 version
    zip
    Bankv6-rrpair.zip   2 KB 1 version


  • 26.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 26, 2018 11:24 PM

    Hi Ulrich,

    Thanks for the reply.

     

    I am facing another issue, my virtual service is running but while running test from manage test is failed , kindly guild me how to handle that.

    Monitor test fail

    monitor 

     



  • 27.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 27, 2018 03:14 AM

    The test was not started with the correct project configuration file. The project configuration file includes - among other information - the port number of the virtual service to connect to. Since the port number is assigned dynamically when creating the virtual service this way, the default project configuration file (project.config) cannot be applied. When creating the baseline test from virtual service, a corresponding project configuration file is created and has to be applied when starting the baseline test using 'Run with options'. As per the screenshots below, once applied with the correct project configuration file, the baseline test executes successfully. Please check out walk-throughs 'Qualify - Create Virtual Service from RR Pairs' or 'Assist - Run Baseline test' from 'Driver Instructions' (bottom left of the Portal), which guide through that process.

    Start of baseline test

    Baseline test execution result



  • 28.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 27, 2018 03:17 AM

    If you have further questions on handling of the SV Test Drive instance, can you please start a new question in this community, because the current discussion does not relate to the topic of this thread anymore.

     

    Thank you.



  • 29.  Re: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

    Posted Apr 20, 2018 07:49 AM

    Hi Brian,

     

    Thanks so much, its working now after updating JRE file.