389-ds-base

#50518 FIPS and password storage schemes
Closed: wontfix by spichugi. Opened by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

This ticket is to discuss the various issues we face with FIPS and password storage schemes. We need to document all the known issues, and provide the necessary steps to move an existing deployment to FIPS, etc.

  • Release note FIPS issues with password schemes. Including replication, data initialization, and upgrade concerns.
  • dsconf should have a FIPS "prepare" task. E.g. set password storage schemes to FIPS approved scheme, and enable password upgrade on bind to reset passwords to FIPS approved scheme.
  • dsconf healthcheck should have a FIPS compliance check option

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.3 (was: 1.4.2)

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/3574

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

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)
Metadata
None
None
None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.