Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)
Previous Next

Only if the second ID file never sync'd with the vault...

If the second copy of the ID file was already "vaulted", then the new password would successfully authenticate to the vault (but not unlock the local ID file). The local ID would be shipped up to the vault server, which could then unlock the client's copy of the ID file, merge it with the vault copy of the ID, then return the merged result to the client, which would then re-encrypt the ID under the new password.

The only time that the old ID will be copied off to the saved IDs directory is when that old ID file had never synchronized with the vault, and so the vault was unable to unlock that ID file. In that case, a copy of the vault's ID is returned to the client, and the client stashes away the old ID file to avoid potential loss of data.

But even in that case, one can log into the old ID with the old password and change the password to match the vault password. That ID will then sync up with the vault and behave as expected in the future.


Feedback response number DKEN7JDUX8 created by ~Ben Umboosichekader on 09/11/2008

IDVault: Documentation Update: If a... (~Patti Lopresak... 11.Sep.08)
. . Only if the second ID file never sy... (~Tanita Desweve... 11.Sep.08)
. . Bug in beta code (~Wei Zeknusonni... 12.Sep.08)




Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS