I have 1 user that gets the “You have a different password on another copy of your ID file and you must change the password on this copy to match” error everytime she changes her password. She is the only person that has this issue. We do use Pistolstar for single-sign on. She is setup the same and uses the same process to change her password, yet everytime it requires me to clear her password digest. No one else has this issue, what am I missing?TIA,
Chris
Subject: Check this
I found this technote http://www-01.ibm.com/support/docview.wss?uid=swg21099995
I would clear the password digest field cut and paste the person doc back in and let it relicate around (thinking you might have rep conflicts)
Also check admin4.nsf db for for request to update password disgest and remove those requests and let that db replicate around. Once all this is done then let the user authenticate to the home server.
Subject: Not a repl conflict
When I make any change I replicate across 3 different servers, so I know it’s not a repl conflict since I would see it at that time. For some reason the password digest field isn’t getting updated. How do I go about checking into this issue? Is that all contained in the admin4 db?
TIA,
-Chris
Subject: Yes admin4.nsf
Check the admin4.nsf db for a request to update the person doc. Check both the home server and admin server for the nab.
If you don’t find a request check the users location doc to make sure the mail server is in canonical format. I have see this as an issues in the past.
Subject: admin4.nsf
Yep - the request is there, so it seems like it should’ve updated, but I had to manually clear out the digest and replicate.
Subject: Ok
Just to be clear the request is in the admin4.nsf on the admin server for names.nsf and it was not processed? Did you try 1) process the request at the console by issuing the Tell adminp process all
If so force a replication and see if the problem is resolved.
If the admin task does not process correctly meaning the person doc does not get updated see if the log shows any error message. I would look to see if it is a rights issue with this person doc.