Closed Therealnaxos closed 2 months ago
Thanks for filing this! Is the client sending certs? If the client sends no certificates at all, the server will reject the handshake entirely and never get to the custom verification callback.
For me locally, if I use openssl s_client
to connect without passing -cert
and -key
, I see an error and the callback isn't called. If I do pass those two arguments, I see the callback invoked appropriately.
Ahh, thanks. You made it clearer to me that a WKWebView cannot accept/handle self signed certificates. So that is probably my core issue.
Will have to figure out another solution for securing my communication between the NIOSSLServerHandler
and the WKWebView
.
Thanks for your help and have a nice day! @Lukasa
It seems like the
customVerificationCallback
does not fire what so ever in the constructor:NIOSSLServerHandler(context: , customVerificationCallback: )
.I have tried setting the
TLSConfiguration
to a bunch of different states/configs. But no combination seem to trigger the custom verification callback.Is this a bug, or a misconfiguration on my part?
Best regards.
Sample code: