This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( 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 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 "", 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 2051628 - JNDI not working with FIPs mode enabled [rhel-8, openjdk-8] [NEEDINFO]
Summary: JNDI not working with FIPs mode enabled [rhel-8, openjdk-8]
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: java-1.8.0-openjdk
Version: 8.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Martin Balao
QA Contact: OpenJDK QA
Depends On:
TreeView+ depends on / blocked
Reported: 2022-02-07 16:22 UTC by Mike Millson
Modified: 2023-09-12 22:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-09-12 22:34:10 UTC
Type: Bug
Target Upstream Version:
mmillson: needinfo? (mbalao)
neugens: needinfo? (mbalao)

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-3433 0 None Migrated None 2023-09-12 22:34:01 UTC
Red Hat Issue Tracker RHELPLAN-111381 0 None None None 2022-02-07 16:34:01 UTC

Description Mike Millson 2022-02-07 16:22:55 UTC
With FIPS enabled, the example code below returns the following exception:

$ java -jar sasl.jar
Callback called
Setting username
Callback called
Setting password
Authentication attempt failed java.lang.IllegalArgumentException: EncryptionKey: Key bytes cannot be null!

Sample code:

1. main method:

LoginContext lc = null;
        try {
            lc = new LoginContext(ServerSasl.class.getName(), new MyHandler());
        } catch (LoginException le) {
            System.err.println("Authentication attempt failed" + le);

        Subject.doAs(lc.getSubject(), new JndiAction(args));

2. implementation

    public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException {
        for (int i = 0; i < callbacks.length; i++) {
            if (callbacks[i] instanceof NameCallback) {
                NameCallback cb = (NameCallback)callbacks[i];
                cb.setName("ADuser realm");
            } else if (callbacks[i] instanceof PasswordCallback) {
                PasswordCallback cb = (PasswordCallback)callbacks[i];
                String pw = "AD user password";
                char[] passwd = new char[pw.length()];
                pw.getChars(0, passwd.length, passwd, 0);
            } else {
                throw new UnsupportedCallbackException(callbacks[i]);

3. implementation


    private static void performJndiOperation(String[] args) {
        Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
        env.put(Context.PROVIDER_URL, "ldap://ldap-server:636");
        env.put(Context.SECURITY_PROTOCOL, "ssl");
        env.put(Context.SECURITY_AUTHENTICATION, "GSSAPI");
        env.put(Context.SECURITY_PRINCIPAL, "ADuser");
        env.put(Context.SECURITY_CREDENTIALS, "ADuser password".getBytes());

        try {
            DirContext ctx = new InitialDirContext(env);

            //Sample query
            System.out.println(ctx.getAttributes("ldap://ldap-server:636", new String[]{"supportedSASLMechanisms"}));

        } catch (NamingException e) {

Comment 10 RHEL Program Management 2023-09-12 22:33:41 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 11 RHEL Program Management 2023-09-12 22:34:10 UTC
This BZ has been automatically migrated to the Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit for general account information.

Note You need to log in before you can comment on or make changes to this bug.