- From: Henry Story <henry.story@bblfish.net>
- Date: Fri, 23 Dec 2011 17:40:57 +0100
- To: WebID XG <public-xg-webid@w3.org>
Ok so I now have a demo of a WebID service that works in a user friendly way with all desktop browsers. Here the issue was to get Safari and Opera to request a certificate from the user if he has one, without showing him an ugly ERROR screen if he does not or refuses. You can try this out now with https://foafssl.org/srv/idp?rs=http://webid.fcns.eu/ The changes this required are listed here https://dvcs.w3.org/hg/read-write-web/rev/23a4ecd7b45d especially see the needyLogin function in https://dvcs.w3.org/hg/read-write-web/diff/23a4ecd7b45d/src/main/resources/template/webidp/idp/util.js Merry Xmas, Henry On 22 Dec 2011, at 15:30, Henry Story wrote: > So by now every desktop browser I have works well with WebID except Opera and Safari. Well > in fact they do work but one has to use the pre TLS-renegotation fix compatibility mode > and the server has to ask for the certificate in NEED mode. I am not sure if this is needed > only on OSX btw, it may be different on Windows. So what is the problem? Well the problem > is that in NEED mode if the client does not have a certificate or cancels the selection then > the web page displayed is going to be an ugly error page that would disconcert non technical > users. > > But I think we have a fix for that. All that is required is to make the authentication > over AJAX for those browsers! I suppose there is a way for the javascript to catch a TLS > error somehow. It can then display an error message nicely saying that no certificate is > available, and ask the user in a friendly manner to do so. > > Any AJAX specialists willing to help me put that together quickly, or point me in the right > direction? > > Henry > > Social Web Architect > http://bblfish.net/ > Social Web Architect http://bblfish.net/
Received on Friday, 23 December 2011 16:41:36 UTC