Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1784147

Summary: crypto/tls: extension (5) error with TLS 1.3 with Go server and Java client
Product: Red Hat Enterprise Linux 8 Reporter: Akram Ben Aissi <abenaiss>
Component: java-11-openjdkAssignee: Martin Balao <mbalao>
Status: CLOSED DUPLICATE QA Contact: OpenJDK QA <java-qa>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: ahughes, gmontero
Target Milestone: rc   
Target Release: 8.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-23 18:01:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1783530    

Description Akram Ben Aissi 2019-12-16 19:49:46 UTC 
As discussed on support-openjdk mailing-list and on https://mail.openjdk.java.net/pipermail/security-dev/2019-December/021036.html

The TLS 1.3 support of OpenJDK 11 has incomplete support for status_request extension in CertificateRequest messages 

A complete reproducer is described here:
https://github.com/golang/go/issues/35722#issuecomment-556949618
Comment 1 Akram Ben Aissi 2020-01-28 07:59:17 UTC 
Hi OpenJDK team. Do we have any update on this ?
Comment 2 Akram Ben Aissi 2020-04-22 09:32:58 UTC 
@Martin Balao: https://bugs.openjdk.java.net/browse/JDK-8236039 is marked as resolved. Is this bz closed then ?
Comment 3 Martin Balao 2020-04-23 00:16:34 UTC 
Yes, 8236039 is shipped as part of 11.0.7 release.
Comment 4 Akram Ben Aissi 2020-06-23 18:01:57 UTC 

*** This bug has been marked as a duplicate of bug 1828939 ***
Comment 5 Andrew John Hughes 2020-07-05 19:43:12 UTC 
Was the fix required here an OpenJDK fix, a Jenkins oauth fix or both?
If it was an OpenJDK fix, it would seem more appropriate to close this bug as CLOSED->CURRENTRELEASE, and make the OpenShift one the dupe.
Comment 6 Red Hat Bugzilla 2023-09-14 05:48:50 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days