I\'m using client certificates in SSL sessions to authenticate users, but I\'m having a bit of a problem with cached sessions. (I have configured IIS to accept—not req
For Chrome (at least in 19.0.1084.30 beta), it seems that, if you can set up a URL on the same hostname that requires a client certificate but rejects all certificates, then making a request to that URL will have the same effect as window.crypto.logout()
. For example, if /ssl_logout/
is the specially-configured URL:
var xmlHttp = new XMLHttpRequest();
xmlHttp.onreadystatechange = function () {
// put any actions to carry out upon logout here
};
xmlHttp.open( "GET", "/ssl_logout/", true );
xmlHttp.send();
(Using a page containing an iframe
or img
with src="/ssl_logout/"
works, too.)
In IE6+:
document.execCommand('ClearAuthenticationCache');
You may be interested in this discussion and this Chromium issue. In particular, you should try:
if (window.crypto) window.crypto.logout();