Notes V11 embedded Sametime SSO broken by Domino’s adminp task?

There where a couple of users who continuously lost their SSO with the embedded Sametime Client in Notes V11. Support told us that the problem was in the HTTPPassword field that was missing. But after we added it again (HTTPPassword=””), by agent suggested by support, after a couple of weeks the same user(s) reported back that SSO was broken again. So it worked for a short period of time. What’s going on in Domino what caused the removal of the HTTPPassword field?

We tracked the timestamp of the PersonDocument modification to the names.nsf’s Administration Server. We discovered that the problem was the “Update client Information” admin process because it was the exact timestamp as we saw for the PersonDocument. After some tests we could reproduce the problem:

1. SSO by LTPA does not need a filled Internet Password. So new users don’t get any Internet Password by creation. This field is created but remains empty.
2. When you work on your laptop, you don’t have any problem
3. When you work in a pool of pc’s (flexible workplace), there the problem occurs.
4. When you logoff from pc A and logon to pc B, an adminp request was created: “Update Client Information”
5. The PC, where you now work on, is added to your PersonDocument in the “Notes Client machine:” field.
6. For some dark reason, an empty field like HTTPPassword is removed. Seems like a misplaced cleanup task.

After this change in your PersonDocument, SSO is broken for your embedded Sametime Client.

When you just add HTTPPassword=”” it only works until the next hop to another PC or after a Client Upgrade.

Visits: 443