As part of our R6 upgrade, we have rolled out password synchronisation with 2000/XP. This is working very well. However…
We have noticed that with password synch turned on, the Logout (and lock)… doesn’t work - it doesn’t lock the ID, and you don’t get the nice screen (no matter how long you leave it). With it turned off (as we have on our laptops for security) it works OK - 30 mins of inactivity locks the ID file.
Is this the way it has been designed? Surely, if you do not have to enter a password to get in to Notes, you will want it to lock out if you leave your PC - its more secure than closing Notes. F5 works OK, but you will not always remember to do this.
Any help/response would be appreciated.
Gavin
Subject: Lock Notes not working with synched passwords
Even with Single Logon installed the client should prompt you for you password if this timeout is enabled.
Dave
IBM
Subject: Is there a point in that?
They could close notes and reopen or am i missing something?
Subject: RE: Is there a point in that?
Yes, I believe you are correct that if they killed Notes with the task manager they could restart notes without being prompted. That of course all takes some amount of time.
The point could be debated, I just responded on how it is designed to work.
Dave
IBM
Subject: RE: Lock Notes not working with synched passwords
Sorry for the delay in responding.
I agree that it should still prompt you for a password - otherwise what is the point of having Notes timeout. In fact, I have Single Sign On installed and working on my machine, F5 locks the ID, and it does prompt you for a password to unlock.
In response to the previous question “How do you know it hasn’t worked?”, when the Notes ID locks out, it clears the screen and shows the Lotus Notes 6 logos (as per pressing F5). This is not happening on a machine with Single Sign On turned on - it is still in the screen (be it inbox, database, whatever) that the user left it in. Therefore, it is not locking out.
With regards to using the Windows Logout screensaver, we run a locked down Windows 2000 environment, part of which disables all screensavers on users desktops. This is because we have had issues in the past with machines crashing with screensavers enabled. Plus, it doesn’t really resolve the original issue - why does Notes not lock the ID after a period of inactivity when Single Sign On is used.
Gavin
Subject: Use a password protected screensaver instead.
Subject: Lock Notes not working with synched passwords
“Surely, if you do not have to enter a password to get in to Notes, you will want it to lock out if you leave your PC - its more secure than closing Notes. F5 works OK, but you will not always remember to do this.”
When the client is locked and you press a key the first thing you have to do is enter the password. Since the single sign-on service will do this, as it does when Notes starts, how do you arrive at the conclusion that using this to lock the client is secure ??
A password protected screensaver, as Vince suggested, is the way to go.