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.
softoken has a built in FIPS login state as well as the login state of individual tokens. For tokens that don't have passwords, softoken needs to simulate those passwords. If softoken is logged in, but the underlying token doesn't know about being logged in, softoken pretends that the token is logged in to the user. This is correct behavior for tokens that don't have login state, but tokens that do have login state, this prevents the underlying token from ever getting logged in.
This creates the problem in slapd described in bug 1352109.
Bug 1387811 works around the problem for slapd, but other uses my still see the error.
It's possible this is also an issue we are seeing in 389-ds-base with replication using SSL client authentication in FIPS mode:
https://bugzilla.redhat.com/show_bug.cgi?id=1464463
Originally we had issues with replication over SSL in FIPS mode, which was resolved, but when we use SSL client authentication it breaks again in FIPS mode.
This bug is only needed if we rebase softoken. The current RHEL-6 has a different login code than RHEL7 and upstream, which support FIPS level 1 semantics.