Friday, September 3, 2021

[389-users] Re: update_pw_encoding messages

On 9/3/21 9:43 AM, Michael Starling wrote:
I see these errors in my logs for some accounts on my consumers with chaining enabled.

- WARN - update_pw_encoding - Could not read password attribute on 'uid=someuser,ou=people,dc=domain,dc=lott'
This means the user does not have a userpassword attribute in its entry.  Can you confirm, on the consumer, if that entry has this attribute? 

Are these spurious messages or something that needs to be addressed?

I came across this:

upgrade-hash is set to "on" on all servers.

What is this code doing?

It's checking if you are using an outdated password storage scheme, and if it is then it re-encodes the password in a more secure algorithm.


int32_t update_pw_encoding(Slapi_PBlock *orig_pb, Slapi_Entry *e, Slapi_DN *sdn, char *cleartextpassword) {
      char *dn = (char *)slapi_sdn_get_ndn(sdn);
      Slapi_Attr *pw = NULL;
      Slapi_Value **password_values = NULL;
      passwdPolicy *pwpolicy = NULL;
      struct pw_scheme *curpwsp = NULL;
      Slapi_Mods smods;
      char *hashed_val = NULL;
      Slapi_PBlock *pb = NULL;
      int32_t res = 0;
      slapi_mods_init(&smods, 0);
       * Does the entry have a pw?
      if (e == NULL || slapi_entry_attr_find(e, SLAPI_USERPWD_ATTR, &pw) != 0 || pw == NULL) {
                        "update_pw_encoding", "Could not read password attribute on '%s'\n",
          res = -1;
          goto free_and_return;


_______________________________________________  389-users mailing list --  To unsubscribe send an email to  Fedora Code of Conduct:  List Guidelines:  List Archives:  Do not reply to spam on the list, report it:  
--   Directory Server Development Team

No comments:

Post a Comment