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.

OpenJDK kerberos implementation lacks behind in terms of modern features/standards. This problem was voiced by kerberos folks in other bug [1].

Lack of support for these was mentioned:
- support modern ccache types (KCM, the default in RHEL 8+, or KEYRING, the default in RHEL 7)
- modern preauth methods (SPAKE)
- futureproof encryption types (AES-SHA2)
- Microsoft compatibility (like NegoEx)

This bug was created to evaluate/discuss this problem.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1966204#c26

@rharwood could you please comment on severenity/priority here? I mean, are we talking mostly about "nice to have" features or are (some of) these urgent in a way, they could (or are known to) cause kerberos to no longer work with Openjdk in the (near) feature?

That's really up to you, and how much you want to be compatible.  For maximum compatibility, switch the default to use krb5 (I think this can be done with sun.security.jgss.native today).

The biggest missing thing is probably ccache types.  If memory serves, the pure-java implementation only supports FILE (and possibly DIR).  The RHEL 8+ default is KCM, and people use KEYRING as well since it's the default in RHEL 7 and serves a different use case.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.