Users are not able to log into any web applications on a server that has recently has Sametime 8.0 added. I see in their Person documents that their Internet Password is changing. Before, and also on all our other servers, if I put in a password like qwertyuiop I see the encrypted password something like (6C9B…B773), and it is always like that, whenever I open the document. On the Sametime server, the encrypted password shows like that when I put it in, but if I save, close and re-open, the password is now garbled (something like (G+12.+a23d+7*-kL7n). Does this explain why we can’t log in? And why is it happening?
Subject: Internet password hash formats
The earlier format that you were seeing was the old, v4.5 http password format. That format was superceded in v4.6 with the “more secure” internet password hash format, which generates a hash along the lines of (G…). Many newer features (such as syncing your internet password with your Notes password) will not work with the older format. We’ve been encouraging people to upgrade hash formats (but couldn’t mandate it, out of respect for backwards compatibility with apps written in v4.5) since v4.6 shipped about a decade ago.
It’s possible that something about the Sametime 8.0 install changed the hash format on that server. I’d recommend upgrading your entire environment to the “more secure” http hash format first, and seeing if that fixes the problem.
Subject: still having difficulaty
David, thanks for the explanation. But we have never run earlier than R6 in this organization, so why did it not happen before. Also, you will see from my post today, we have persistent problems with browser logins. If you have any more ideas, please share.