Hi
I am running PWB V2.08.4 as a kiosk in a Library. The Wyse terminal auto logs onto a Windows RDT system and starts PWB. This works fine for all of the required browsing but when a staff member requests a photocopy they are required to provide their windows domain login details. This then populates the request page with their details and the staff member can provide the details of the copy.
All works perfectly except that when the library visitor walks away, even though they may set the page back to home, the next time someone uses the photocopy request page, the previous user is still logged in with their details plain to see.
Any ideas on how to stop this bar closing the browser and forcing a re-start?
Thanks
Scott
PWB remembers previous users login details
Moderators: Tyler, Scott, PWB v2 Moderator
Hi
PWB is connecting to our corporate web pages and as part of the Library Services, a library visitor may request copies of a document.
If the visitor is a CSIRO staff member, they use their domain logon credentials and the web page then populates the request page with details extracted from the AD.
The main issue is that even though this happens in a second window which the user then closes, an subsequent user going to the same page will automatically be logged in as the previous user.
Completely closing PWB and re-starting the terminal does the job but staff have to REMEMBER to do this.
Thanks
PWB is connecting to our corporate web pages and as part of the Library Services, a library visitor may request copies of a document.
If the visitor is a CSIRO staff member, they use their domain logon credentials and the web page then populates the request page with details extracted from the AD.
The main issue is that even though this happens in a second window which the user then closes, an subsequent user going to the same page will automatically be logged in as the previous user.
Completely closing PWB and re-starting the terminal does the job but staff have to REMEMBER to do this.
Thanks
It sounds as if the web site is using a session variable, or some other kind of persistence, to make the site easier to use by not making a person log on each time. Unfortunately this causes a problem when you do not want this behavior. If you could determine how the site is remembering the user you may be able to set up Internet Explorer, and thusly PWB, to prevent it, such as disabling the cookies.
This site talks about why persistent variables won't stick, perhaps you can apply the methods in reverse.
http://classicasp.aspfaq.com/general/wh ... stick.html
We use the PWB inactivity timer, clear cache on close, restart on close, a close PWB shellbar button , and encourage our patrons to close PWB for security reasons, to give each user a "fresh" browser with not persistent variables, and no links visited.
--Scott
This site talks about why persistent variables won't stick, perhaps you can apply the methods in reverse.
http://classicasp.aspfaq.com/general/wh ... stick.html
We use the PWB inactivity timer, clear cache on close, restart on close, a close PWB shellbar button , and encourage our patrons to close PWB for security reasons, to give each user a "fresh" browser with not persistent variables, and no links visited.
--Scott