Wew are still using findSlotbyName() which does not work correctly in FIPS mode as FIPS changes the internal token name. Instead just get the internal slot
Tentative patch, needs more testing...
<img alt="0001-Issue-50588-Address-tokenname-issues-impacting-FIPS.patch" src="/389-ds-base/issue/raw/files/fcb212ab370214f787455ac950bb6611dcb7a333b895c20cb2e006cd2daacce2-0001-Issue-50588-Address-tokenname-issues-impacting-FIPS.patch" />
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Doesn't look insane to me, but I'm really not familiar with this part of the codebase. Testing is probably wise :) Maybe some of the affected users on ML's could test the patch?
Well this is the same type of code change used in DS. We can not use PK11_GetTokenByName, as FIPs changes the internal token name. So it theory this should fix that part of it, but I don't know if that is the same problem the community member was having. I have reached out to the community member and even provided a scratch build for him to test. No response yet, but I hope to hear something soon.
Metadata Update from @mreynolds: - Issue set to the milestone: Legacy
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3644
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.