In the krb5 tests sun/security/krb5/ktab/KeyTabIndex.java and FileKeyTab.java we get the following exception

KrbException: no supported default etypes for default_tkt_enctypes
at java.security.jgss/sun.security.krb5.Config.defaultEtype(Config.java:1015)
at java.security.jgss/sun.security.krb5.internal.crypto.EType.getDefaults(EType.java:264)
at java.security.jgss/sun.security.krb5.EncryptionKey.acquireSecretKeys(EncryptionKey.java:180)
at java.security.jgss/sun.security.krb5.internal.ktab.KeyTab.addEntry(KeyTab.java:377)
at java.security.jgss/sun.security.krb5.internal.ktab.KeyTab.addEntry(KeyTab.java:370)
at KeyTabIndex.main(KeyTabIndex.java:38)

This is seen on a RHEL 8 system, with the following krb5 configuration (which is setting permitted_enctypes to an empty list).

more /etc/krb5.conf.d/crypto-policies
[libdefaults]
permitted_enctypes =

This config leads to no supported default etypes (default_enctypes is not null but empty in
public int[] defaultEtype(String configName) in src/java.security.jgss/share/classes/sun/security/krb5/Config.java).
If this is really the desired behavior we should maybe adjust the test so that a KrbException like this is not failing the test ?