Adding Identity Provider

[nicola]

Fixes #105

Ready to merge (only after linkeddata/node-webid#9 is merged and published on NPM)

This has been a lot more fun (and a lot more work!) than we thought.

Things left to do:

• certificate creation (@sible777 helped)
• availability of subdomain storage (right now the "api" to create an account work, but one can't really access it yet - I have to enable ldp on subdomains!)
• support for multiple hosts
• make it work with solid-signup
• creating an account and use the same session to request the certificate
• fix the test that currently has a TLS error (maybe because the certificate is for one domain only)

Things left to do in new PRs:

• creation of workspace, preference files, inbox.. (this should be just piping)
• certificate lost / stolen, how to get a new one? Account recovery via email #175

[corysabol]

creating an account and use the same session to request the certificate @nicola

This is something that I too would like to understand better! I tried implementing some stuff like this recently and the only way I could figure to do it was to have the certificate request come from a different domain/provider.

Let me know what you figure out 👍

[nicola]

Ok, when tested with linkeddata/node-webid#9 it works. However, we need to merge linkeddata/node-webid#9 and update the version of webid in the package.json before merge

[deiu]

I wonder if we can add a test here to check if the user can login with the new cert -- i.e. get the same WebID from the User header, following an authenticated request.