On 09.05.2018 17:21, Marc Muehlfeld wrote:
The problem is that the upgrade script doesn't enable the plug-in if the
instance was installed using 1.3.5 or earlier.
I filed a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1576485
Mark fixed this upstream: https://pagure.io/389-ds-base/issue/49665
To manually add the missing entry:
# ldapadd -D "cn=Directory Manager" -W -x
dn: cn=PBKDF2_SHA256,cn=Password Storage Schemes,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
cn: PBKDF2_SHA256
nsslapd-pluginPath: libpwdstorage-plugin
nsslapd-pluginInitfunc: pbkdf2_sha256_pwd_storage_scheme_init
nsslapd-pluginType: pwdstoragescheme
nsslapd-pluginEnabled: on
nsslapd-pluginDescription: Salted PBKDF2 SHA256 hash algorithm
(PBKDF2_SHA256)
nsslapd-pluginVersion: 1.3.7.5
nsslapd-pluginVendor: 389 Project
nsslapd-pluginId: pbkdf2-sha256-password-storage-scheme
adding new entry "cn=PBKDF2_SHA256,cn=Password Storage
Schemes,cn=plugins,cn=config"
After a restart of the instance, you can use the password storage scheme:
# ldapmodify -D "cn=Directory Manager" -W -x
dn: cn=config
changetype: modify
replace: passwordStorageScheme
passwordStorageScheme: PBKDF2_SHA256
modifying entry "cn=config"
Regards,
Marc
--
Marc Muehlfeld
Senior Technical Writer, Customer Content Services
Red Hat GmbH
Technopark II,
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
Email: mmuehlfeld@xxxxxxxxxx
_______________________________________________________________________________
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham,
Michael O'Neill, Eric Shander
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
