W3C home > Mailing lists > Public > public-webid@w3.org > September 2015

Re: Node.js WebID implementation

From: Miel Vander Sande <Miel.VanderSande@ugent.be>
Date: Mon, 7 Sep 2015 14:09:15 +0200
Message-Id: <BDFFA5B2-4A04-41E7-B6B9-9607D512650E@ugent.be>
To: public-webid@w3.org
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?

Kind regards,

Miel Vander Sande
Researcher Semantic Web - Linked Open Data
Multimedia Lab [Ghent University - iMinds]

T: +32 9 33 14893

Received on Monday, 7 September 2015 12:09:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:59 UTC