W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

Re: WebIDRealm Debug Section

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Fri, 06 Jan 2012 17:03:24 -0500
Message-ID: <4F076FAC.1090408@openlinksw.com>
To: Jürgen Jakobitsch <j.jakobitsch@semantic-web.at>
CC: public-xg-webid@w3.org
On 1/6/12 4:36 PM, Jürgen Jakobitsch wrote:
> hi kingsley,
>
> the debug section now always does a
>
> session.invalidate() and the javascript:logout thing.
> so in fact you're logged in for the test to run and logged out at the end of the test.
>
> i still have some confusion with links in the menu, but that will be fixed soon.

Okay.

>
> btw : i think we all use sort of the same js code to log out [1]
>        is this window.crypto thing or the "AuthenticationCache" something
>        different that a cookie?
>        i asking because, i clear the authentication cache with my site,
>        it seems that the person coming to my site has to log in to other sites again also,
>        which i would consider suboptimal.
>
> wkr j
>
>
> [1] function logout() {
>       if (document.all == null) {
>        if (window.crypto) { window.crypto.logout(); }
>       } else {
>        document.execCommand('ClearAuthenticationCache');
>       };
>      }
We don't re. our verifier. At the current time, we are opting to be 
consistently inconvenient across all browsers, for now :-)

Kingsley

>
> ----- Original Message -----
> From: "Kingsley Idehen"<kidehen@openlinksw.com>
> To: public-xg-webid@w3.org
> Sent: Friday, January 6, 2012 9:43:13 PM
> Subject: Re: WebIDRealm Debug Section
>
> On 1/6/12 11:40 AM, Jürgen Jakobitsch wrote:
>> Hi,
>>
>> Kingsley wrote in one of the last mail with subject "WebIDRealm RDFa"
>>
>>> What we need is a debugger for WebID. Something like:
>>>
>>> 1. http://validator.linkeddata.org/vapour -- debugs the Name/Address
>>> disambiguation issue re. HTTP URIs re. Linked Data
>>> 2. http://linkeddata.informatik.hu-berlin.de/uridbg/ -- debugs HTTP URIs
>>> in general .
>> i have added a debug section on WebIDTestServer [1] (see "Debug" in the menu).
>> it gives a summary of all exceptions that i catch in the code and groups them
>> to topics.
>> i'm sure there are things that i didn't consider - but it should give an idea
>> what wrong with a webIDClaim and certificate.
>>
>> if you wanna give it a try, simply edit your profile to see some of the exceptions and relogin.
>>
>> for example :
>>
>> if you replace "cert:key" with "cert:Xkey" and relogin, you should see "Is cert:key found?"-test red.
>>
>> hope that helps...
>>
>> wkr http://www.turnguard.com/turnguard
>>
>> [1] http://webid.turnguard.com/WebIDTestServer/
>>
>>
>>
>> --
>> | Jürgen Jakobitsch,
>> | Software Developer
>> | Semantic Web Company GmbH
>> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
>> | A - 1070 Wien, Austria
>> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>>
>> COMPANY INFORMATION
>> | http://www.semantic-web.at/
>>
>> PERSONAL INFORMATION
>> | web   : http://www.turnguard.com
>> | foaf  : http://www.turnguard.com/turnguard
>> | skype : jakobitsch-punkt
>>
>>
> Jurgen,
>
> I presented a cert. that I expected to fail to this service. The failure
> happened. Unfortunately thoughg,  I've been unable to reuse the service
> using a different identity.
>
> You seem to be associating my identity with a browser cookie or
> something along those lines.
>
> When I close and reopen my browser, I expect to have the ability to
> restart the entire WebID based challenge cycle using alternative
> identities via their associated x.509 certs .
>


-- 

Regards,

Kingsley Idehen	
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen








Received on Friday, 6 January 2012 22:06:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 6 January 2012 22:06:25 GMT