If you are using mqweb using certificates to identify yourself, if you logoff, or close the tab, then open a new tab, you will get a session using the same certificate as before.
This little problem has been a tough one to investigate, and turns out to be lack of function in Chromium browser.
The scenario is you connect to mqweb using a digital certificate. You want to logoff and logon again with a different certificate, for example you do most of your work with a read only userid, and want to logon with a more powerful id to make a change. You click logoff, and your screen flashes and logs you on again with the same userid as before.
At first glance this may look like a security hole, but if someone has access to your web browser, then the can click on the mqweb site, and just pick a certificate – so it is no different.
Under the covers, the TLS handshake can pass up the previous session ID. If the server recognises this, then it is a short handshake instead of a full hand shake, so helping performance.
To reset the certificate if you are using Firefox
To clear your SSL session state in Firefox choose History -> Clear Recent History… and then select “Active Logins” and click “OK”. Then the next time you connect to your SSL server Firefox will prompt for which certificate to use, you may need to reset the URL.
You should check Firefox preferences, certificates, “Ask you every time” is selected, rather than “Select one automatically”.
Chrome does not support this reset of the certificate.
There has been discussion over the last 9 years along the lines of, seeing as Internet Explorer, and Firefox have there, should we do it to met the end user demand?
If you set up an additional browser instance, you get the same problem. With Chrome you have to close down all instances of the browser and restart chrome to be able to select a different certificate.
It looks like there is code which has a cache of url, and certificate to use. If you open up another tab using the same IP address you will reuse the same certificate.
If you localhost instead of 127.0.0.1 – it will prompt for certificate, and then cache it, so you can have one tab open with one certificate, and another tab, with a different URL and another certificate.