[
https://issues.apache.org/jira/browse/DERBY-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernt M. Johnsen updated DERBY-3096:
------------------------------------
Attachment: DERBY-3096.stat
DERBY-3096.diff
Sun has interpreted the JSSE spec somewhat differently than e.g. IBM and does
not intend to change this. I workaround with an explicit default key store has
been found for Sun's JSSE. The patch need somewhat more testing before commit.
> SSL handshake throws "bad_certificate" when server tries to authenticate
> client
> -------------------------------------------------------------------------------
>
> Key: DERBY-3096
> URL: https://issues.apache.org/jira/browse/DERBY-3096
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server, Security
> Affects Versions: 10.3.1.4
> Reporter: Bernt M. Johnsen
> Assignee: Bernt M. Johnsen
> Fix For: 10.3.2.0, 10.4.0.0
>
> Attachments: DERBY-3096.diff, DERBY-3096.stat, SslTest.zip
>
>
> When the server runs with -ssl peerAuthentication and the client with -ssl
> basic the SSL handshake gives the error "bad_handshake", e.g. when server
> shutdown is used:
> Could not connect to Derby Network Server on host localhost, port 1527:
> Received fatal alert: bad_certificate
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
