- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Mon, 7 Sep 2015 16:55:38 +0200
- To: Miel Vander Sande <Miel.VanderSande@ugent.be>
- Cc: public-webid <public-webid@w3.org>
Received on Monday, 7 September 2015 14:56:06 UTC
On 7 September 2015 at 14:09, Miel Vander Sande <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 > > > 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 14:56:06 UTC