반응형
https 테스트 시, 서버에서 SSLHandshakeException 에러가 발생하는 경우 해결법
1. Server
Caused by: javax.net.ssl.SSLHandshakeException: No available authentication scheme
at sun.security.ssl.Alert.createSSLException(Alert.java:131)
at sun.security.ssl.Alert.createSSLException(Alert.java:117)
at sun.security.ssl.TransportContext.fatal(TransportContext.java:314)
at sun.security.ssl.TransportContext.fatal(TransportContext.java:270)
at sun.security.ssl.TransportContext.fatal(TransportContext.java:261)
at sun.security.ssl.CertificateMessage$T13CertificateProducer.onProduceCertificate(CertificateMessage.java:956)
at sun.security.ssl.CertificateMessage$T13CertificateProducer.produce(CertificateMessage.java:945)
at sun.security.ssl.SSLHandshake.produce(SSLHandshake.java:420)
at sun.security.ssl.ClientHello$T13ClientHelloConsumer.goServerHello(ClientHello.java:1100)
at sun.security.ssl.ClientHello$T13ClientHelloConsumer.consume(ClientHello.java:1034)
at sun.security.ssl.ClientHello$ClientHelloConsumer.onClientHello(ClientHello.java:716)
at sun.security.ssl.ClientHello$ClientHelloConsumer.consume(ClientHello.java:683)
at sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:376)
at sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:451)
at sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run(SSLEngineImpl.java:987)
at sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run(SSLEngineImpl.java:974)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.ssl.SSLEngineImpl$DelegatedTask.run(SSLEngineImpl.java:921)
at io.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:1460)
at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1365)
at io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1199)
at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1243)
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:502)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:441)
... 15 common frames omitted
2. Client
이때, Client는 postman API를 이용하였다.
postman에서는 'Error: Client network socket disconnected before secure TLS connection was established' 에러가 발생한다.
[해결방법]
서버 쪽에 저징되어 있는 keyStore가 잘못세팅되어 있던 경우로, server용 keystore를 변경하면 된다.
server.jks파일로 등록되어있던 keystore resourse를 server로 변경 후 실행하였더니 에러가 발생하지 않았다.
반응형
'WEB' 카테고리의 다른 글
Postman 테스트 시, WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc 발생 (0) | 2020.10.15 |
---|---|
Https 로컬 용 Keystore 생성 및 Camel ssl 적용 방법 (0) | 2020.10.13 |
CSS Selector (0) | 2020.06.28 |
HTML5 - WebSockets (0) | 2020.06.28 |
jQuery Event Methods (0) | 2020.06.28 |