maxWait% -- An integer constant that must be set to the number of minutes to wait before a pop-up appears for the user to log in again. The value should be less than the SSO expiration time.
msgText$ -- A string constant that defines the text information that will appear in the body of the pop-under window.
titleText$ -- The string constant used to define the title of the browser's pop-under window.
fileName$ -- The string constant that defines the NSF file which contains the agent. (Include relative path information in the NSF name. For example, utilsMyNsfFile.nsf.)
popupText$ -- The string constant that defines the text which will appear in the alert message when the SSO expiration time -- maxWait% time elapses.
There is also a string variable called urlRedirect$. It contains the value "SSOTimer" as the name of the agent. Replace "SSOTimer" to the same name you gave to your agent that contains the code.
The agent should have the following settings:
When should this agent run? = Manually from agent list
Which document(s) should it act on? = Run once (@Commands may be used)
The agent will detect if it was called from a parent window. If so, focus will be returned to the parent window after the user responds to the alert message and logs onto the server again.
In summary, the process works as follows:
- User logs into Web application and triggers the agent to run in a pop-under window.
- The pop-under window waits for the specified period of time and then alerts the user with a user defined message.
- User logs in with user name and password again (refreshingSSO expiration time).
- Focus is returned to the parent window.
I tried this tip last fall, but didn't like the pop-up window being launched at the same time the user logs in. By the time the window is actually needed, many users would have closed the background pop-up window. It's not the normal way timers work on web-sites, so you would have to train your users and some would complain that it should work the way every other site works.
I personally think Lotus should build an inactivity timer into the Domino web server and it should work regardless of whether or not SSO is turned on. I don't understand why this wasn't available several years ago.
Speaking of SSO, we used it for a short while, but decided to turn it off when we realized we couldn't use an IP address to get to the server with this feature on. Occasionally, someone who is traveling will have DNS problems and being able to use an IP address as opposed to a fully qualified host name is an essential back door to get to webmail.
This is something I have been seeking for a while. Will this run in R5? May I please have a sample database with this code contained in it?
Yes, the code will work on R5. I intentionally made the functionality work with an agent, so you would not have to worry about extra steps to implement what the agent does.
—Dennis Potts, tip author
Addendum -- tip author Dennis Potts e-mailed us on May 6 with this message: The pop-under window does not close if the parent window is closed. If a pop-under window is left open and becomes an orphan when the parent closes, a premature pop-up alert will still move to the background, but it is a little confusing to users to see the alert as soon as they log onto a new parent window.
Dennis has submited an update that will close the pop-under window when the parent is closed. Click here to view that update.
Do you have comments on this tip? Let us know.
This tip was submitted to the SearchDomino.com tip exchange by member Dennis M. Potts Jr. Please let others know how useful it is via the rating scale below. Do you have a useful Notes/Domino tip or code to share? Submit it to our monthly tip contest and you could win a prize and a spot in our Hall of Fame.