- From: Nicola Greco <me@nicolagreco.com>
- Date: Tue, 8 Sep 2015 18:24:33 -0400
- To: bergi <bergi@axolotlfarm.org>
- Cc: Miel Vander Sande <Miel.VanderSande@ugent.be>, public-webid@w3.org
- Message-Id: <FDC08EF5-4841-4647-8731-9DBE7367810B@nicolagreco.com>
@Miel
Are you sure you have everything set to request the certificate?
you have to pass requestCert = true in the createServer options in https
https.createServer({
key: key,
cert: cert,
requestCert: true
}, app);
Let me know,
Nicola Greco
- Keep on rocking the free web
> 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
>
> Am 07.09.2015 um 14:09 schrieb Miel Vander Sande:
>> 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 Tuesday, 8 September 2015 22:26:35 UTC