<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Just wondering if anyone has had much success with the Kerberos Login Handler and Chrome (on Mac and Linux (Debian))?</div>
<div><br>
</div>
<div>We have successfully configured for all other browsers – & even Chrome on Windows is working. The doco has proven most helpful: https://wiki.shibboleth.net/confluence/display/SHIB2/Single+sign-on+Browser+configuration</div>
<div><br>
</div>
<div>What is strange is Chrome appears to be successfully obtain service tickets (running klist at certain points confirms this) - running a tcpdump on the client and server seem to indicate all is well. Cannot see a difference between traffic sent by other
browsers and Chrome – however after Chrome sent the Kerberos ticket the Login Handler ends up doing whatever it does to make request.getAttribute("krbLoginFailed") true – whereas the other browser signs on with the same Service Ticket.</div>
<div><br>
</div>
<div>We've tried various other options to feed Chrome on the command like – it's not changing any behaviour as far as we can see</div>
<div><br>
</div>
<div>Mainly am bit confused by it all – at the moment it'd just be good to hear if other have it working or have had trouble too. </div>
<div><br>
</div>
<div>Cheers</div>
<div>Aaron</div>
</body>
</html>