Sneak peak - the Domino 8.5 id vault
Category
This, in short, is a feature that will have Domino administrators, help desk staff and help desk managers dancing in the aisle at Lotusphere. While playing around with the beta, I setup and configured the id vault and thought I would post some screenshots/thoughts. And, of course its a beta, so what you see here may not be what you get!
It requires Notes 8.5 on the server and client.
Im not going to go into details on how it works just yet, but I had it up and running in about 10 minutes in a lab.
Administrators can create one, or multiple vault databases to store passwords, and assign id files created by specific Organisation units to the databases. Admins have to also be assigned rights to reset passwords, and these rights can be vault specific.
From a users' perspective, what does the id vault let you do. Well, two simple things at the moment.
1 - It allows you to change your password on your Notes client, and that, in turn means your password is changed on any other copy of your id file from now on.
2 - It allows you to easily get your password reset.
From an administrator's perspective, it gives us the functionality to:
Keep an storage of id files in an encrypted database on the server. These id files are provisioned to the notes clients upon logon (i.e. the id file is sent down to the client). When a user changes his password, the id file goes up to the vault/database with the new password, so if he logs on from another machine, the updated id file is sent down (ergo - password syncing accross Lotus Notes clients).
Have custom, policy based information given to users telling them how to ask to have their password reset.
Reset the password in two clicks.
Here are some pictures of what the user can see:
Note the Forgotton password button! We can give customised messages to the clients based on policies applied, for example:
Now, what does an administrator have?, well, from the people tab of the client, permitted Administrators are allowed do this:
And then do this:
And, it works... even in beta. I have reset the password and immediately the user can log in using that password. Nice eh?
This, in short, is a feature that will have Domino administrators, help desk staff and help desk managers dancing in the aisle at Lotusphere. While playing around with the beta, I setup and configured the id vault and thought I would post some screenshots/thoughts. And, of course its a beta, so what you see here may not be what you get!
It requires Notes 8.5 on the server and client.
Im not going to go into details on how it works just yet, but I had it up and running in about 10 minutes in a lab.
Administrators can create one, or multiple vault databases to store passwords, and assign id files created by specific Organisation units to the databases. Admins have to also be assigned rights to reset passwords, and these rights can be vault specific.
From a users' perspective, what does the id vault let you do. Well, two simple things at the moment.
1 - It allows you to change your password on your Notes client, and that, in turn means your password is changed on any other copy of your id file from now on.
2 - It allows you to easily get your password reset.
From an administrator's perspective, it gives us the functionality to:
Keep an storage of id files in an encrypted database on the server. These id files are provisioned to the notes clients upon logon (i.e. the id file is sent down to the client). When a user changes his password, the id file goes up to the vault/database with the new password, so if he logs on from another machine, the updated id file is sent down (ergo - password syncing accross Lotus Notes clients).
Have custom, policy based information given to users telling them how to ask to have their password reset.
Reset the password in two clicks.
Here are some pictures of what the user can see:
Note the Forgotton password button! We can give customised messages to the clients based on policies applied, for example:
Now, what does an administrator have?, well, from the people tab of the client, permitted Administrators are allowed do this:
And then do this:
And, it works... even in beta. I have reset the password and immediately the user can log in using that password. Nice eh?
- 
Comments
But what happens if my designers want to test something with the id of another user. Since now they get the id of the user with the initial password from our store and log in and test.
Is something like this still possible with the vault?
Posted by Matthias At 16:55:07 On 25/08/2008 | - Website - |
Posted by Paul Mooney At 16:58:18 On 25/08/2008 | - Website - |
Posted by Jan Van Puyvelde At 19:33:19 On 25/08/2008 | - Website - |
Posted by paul At 19:41:47 On 25/08/2008 | - Website - |
Posted by Chad At 13:37:13 On 26/08/2008 | - Website - |