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: Wed, 9 Sep 2015 14:58:55 +0200
Cc: bergi <bergi@axolotlfarm.org>, public-webid@w3.org
Message-Id: <FE243D30-89E2-4320-A074-A49D29BBF36A@ugent.be>
To: Nicola Greco <me@nicolagreco.com>
Hi all,

Thanks for the help!

On 09 Sep 2015, at 00:24, Nicola Greco <me@nicolagreco.com> wrote:
> you have to pass requestCert = true in the createServer options in https

Yes, that's what I'm doing. My question is about the parsing of the certificate.

>> On Sep 8, 2015, at 5:32 PM, bergi <bergi@axolotlfarm.org> wrote:
>> Have you tried pubkey-login [1]? I developed it for LDApp [2]. I tried
>> it a few days ago with the latest Node.js and io.js versions. Still
>> works for me.
>> [1] https://github.com/bergos/pubkey-login/
>> [2] https://github.com/bergos/ldapp

Great, that will help me pinpoint the problem.
Basically, I want to be able to do this: https://github.com/bergos/pubkey-login/blob/master/pubkey-login.js#L93 since I'm doing this https://github.com/bergos/pubkey-login/blob/master/pubkey-login.js#L85.
However, the property subjectaltname does not exist in the object returned by getPeerCertificate() (others do) when it's included in the X509 extensions. So i'm wondering wether I'm missing a parameter somewhere that makes nodejs also parse the X509 extensions properties. Could you perhaps provide an example certificate that works with your implementation?


Received on Wednesday, 9 September 2015 12:59:31 UTC

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