RE: Authentication workflow draft.

Yes, it's time for a restful web service (supported by https client authn and SSL session management) that takes a base64 encode cert as input, and returns YES/NO 

The input parser should assume the worst: strange CRLF or LR or CR, random header text, variable number of dashes, missing final EOL, UTF header bytes, web friendly char sets or ascii - so as to deal with the realty of "PEM encoding"

Another variant would take a cert sha1 fingerprint, rather than the cert.

-----Original Message-----
From: public-xg-webid-request@w3.org [mailto:public-xg-webid-request@w3.org] On Behalf Of Kingsley Idehen
Sent: Tuesday, April 12, 2011 9:29 AM
To: peter williams
Cc: 'Andrei Sambra'; 'WebID XG'
Subject: Re: Authentication workflow draft.

On 4/12/11 12:14 PM, peter williams wrote:
> This is relevant to me, as it means for each URI in the SAN, I do a uriburner query, which (remotely) looks for a cert:identity match for 1 card at a time.
>
> Can sparql have multiple FROM lines? Perhaps?

Yes, re. Virtuoso's SPARQL support.

>   Can the query be modified so Id know which URI matched, if one could specify multiple matches?

Yes.

I am guessing its time for a WebID verification service. Ditto email verification service as spec'd by Toby a while back.

-- 

Regards,

Kingsley Idehen 
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen

Received on Tuesday, 12 April 2011 17:00:49 UTC