389-ds-base

#49862 EncryptionAlgorithm attributes have two different names but the same purpose
Closed: wontfix by spichugi. Opened by spichugi.

Closed: wontfix
Reopen Issue

When we set up the encryption algorithm in changelog5 entry, we use nsslapd-encryptionalgorithm attribute:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/configuration_command_and_file_reference/index#cnchangelog5-nsslapd-encryptionalgorithm_Encrytion_Algorithm

And when we set up the attribute encryption we use nsEncryptionAlgorithm:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/configuration_command_and_file_reference/index#Database_Attributes_under_cnattributeName_cnencrypted_attributes_cndatabase_name_cnldbm_database_cnplugins_cnconfig

These attributes have the same purpose.
I think it's worth a discussion if we should deprecate one of them or do something about it.
It is already used by customers so we should be careful with the decisions, of course.

Metadata Update from @spichugi:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue priority set to: minor

If we want to deprecate one (i.e. nsEncryptionAlgorithm) we could support nsslapd-encryptionalgorithm and nsEncryptionAlgorithm for attribute encryption for the same meaning.
And document that one will be deprecated in next major release.
On next major release remove the support of deprecated one and its schema definition.

But I am not sure it worth the effort.

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

Metadata Update from @mreynolds:
- Issue priority set to: major (was: minor)
- Issue set to the milestone: 1.4.3 (was: 1.4.1)

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

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
Normal
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.