#49766 passwordStorageSchema attribute
Closed: wontfix Opened by d3ag0s.

Issue Description

Setup passwordStorageSchema attribute with ldapmodify, doesn't recognize the attribute:

ldapmodify -x -D "cn=Directory Manager" -W <<!

dn: cn=config
changetype: modify
replace: passwordStorageSchema
passwordStorageSchema: sha
!
Enter LDAP Password:
modifying entry "cn=config"
ldap_modify: Server is unwilling to perform (53)
additional info: Unknown attribute passwordstorageschema will be ignored

Other attributes (such as nsslapd-security, nsslapd-allow-hashed-passwords) are setup correctly.

Package Version and Platform

389-ds-1.2.2-6, CentOS7

Steps to reproduce

  1. Install 389-DS latest version
  2. Setup a default instance
  3. Try to set the passwordStorageSchema attribute

If the entry is inserted manually in dse.ldif under dn: cn=config / cn: config, this works just fine.

Actual results

Expected results


You want to use "passwordStorageScheme" not "passwordStorageSchema". Note the Scheme vs Schema

Metadata Update from @mreynolds:
- 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

Metadata Update from @d3ag0s:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

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

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 (was: invalid)

Metadata