If we switch from SSO to shared login and windows is now controlling the password, why do we need the additional overhead of an ID Vault ? If a user forgets their password then the help desk support would quickly reset it at the network level supporting the Notes login. There doesn’t seem to be a need for the ID Vault unless there is a reason. - Thanks.
Subject: ID vault
The ID vault is a secure, centralized, server-based repository for storing and managing ID files.
In addition to streamlining the password reset process, the ID vault can be used for
-
easy recovery of lost or damaged user ID files.
-
provisioning ID files to new users.
-
automatic synchronization of multiple copies of the ID file.
-
an “Auditor” function to provide an ID file for legal discovery/access to encrypted data.
-
simplification of user key rollover, renames, and organizational moves.
See the ID vault overview FAQ.
Subject: Unclear
I understand the FAQ’s on ID Vault, have set it up and replicated. But we use SSO not Shared Login. Shared login uses the microsoft directory for maintaining passwords so why would we want to use the ID Vault to do what is an easier operation by a standard help desk function ? Shared login also abandons the auto update of HTTP passwords requiring us to rig up directory assistance with LDAP. We also use traveler in a DMZ which relies on the NAB being pushed into the DMZ to access the HTTP password, not an internal LDAP directory. I see the valus of SSO and the ID Vault but fail to see the value of the ID Vault with shared login.
Subject: Accidentally deleted ID files. Crashed hard drives. Computers gone missing.
Life is uncertain. Backups of critical data – like ID files – are important, and the Notes ID vault gives you an encrypted, up-to-date backup of your ID files that is more feature-rich and easier to use and administer than ID file recovery.