- From: Miel Vander Sande <miel.vandersande@ugent.be>
- Date: Tue, 8 Sep 2015 18:50:18 +0200
- To: Andrei Sambra <andrei@w3.org>
- Cc: public-webid@w3.org
- Message-Id: <9C2DC8A1-F677-4581-8484-0DA58571F84D@ugent.be>
Thanks all, these are nice examples. However, this library expects a "certificate" (https://github.com/linkeddata/node-webid/blob/master/index.js#L11), but getting that raw certificate from the HTTPS connection is what I'm after (X509 extensions properties currently not accessible). For now, I've implemented it using the regular non-X509 subject alt name field. Miel On 08 Sep 2015, at 17:26, Andrei Sambra <andrei@w3.org> wrote: > > > On 9/7/15 10:55 AM, Melvin Carvalho wrote: >> >> >> On 7 September 2015 at 14:09, Miel Vander Sande >> <Miel.VanderSande@ugent.be <mailto:Miel.VanderSande@ugent.be>> wrote: >> >> Hi all, >> >> Time to revamp this old thread. Does anyone know on any progress or >> workarounds in this regard? >> The request.connection.getPeerCertificate() still doesn't seem to >> return any X509 extensions, hence the client's WebID cannot be >> extracted from the Subject Alternative Name. >> I also looked at the Forge >> (https://github.com/digitalbazaar/forge) library, but that seems >> like a lot of overhead compared to https library. >> >> Or is there a way to get the raw certificate from the client and >> parse it with a library like this https://www.npmjs.com/package/x509? >> >> >> Or this >> >> https://github.com/magnetik/node-webid/blob/master/src/VerificationAgent.coffee > > Actually, that repo hasn't been maintained in a while and it is buggy. > You should use the updated version at > https://github.com/linkeddata/node-webid instead. > > --Andrei > >> >> >> >> >> Kind regards, >> >> Miel Vander Sande >> Researcher Semantic Web - Linked Open Data >> Multimedia Lab [Ghent University - iMinds] >> >> T: +32 9 33 14893 >> >> >> >> > > -- > Andrei Sambra > World Wide Web Consortium > Cambridge, MA > Tel. 617-253-5565 >
Received on Tuesday, 8 September 2015 16:50:49 UTC