I can run single-user mode server now with a bug which somehow can be skipped in single-user mode but cannot be ignored in multi-user mode. Here is my setup steps:
- git clone https://github.com/solid/node-solid-server
- cd node-solid-server
- mkdir build
- pushd build
- openssl req -newkey rsa:2048 -nodes
-x509 -days 365
- …/bin/solid init
$ ? Path to the folder you want to serve. Default is <… …> [return]
$ ? SSL port to run on. Default is [return]
$ ? Solid server uri (with protocol, hostname and port) [return]
$ ? Enable WebID authentication [return]
$ ? Serve Solid on URL path [return]
$ ? Path to the config directory (for example: /etc/solid-server) [return]
$ ? Path to the config file (for example: ./config.json) [return]
$ ? Path to the server metadata db directory (for users/apps etc) [return]
$ ? Path to the SSL private key in PEM format ./domain.key
$ ? Path to the SSL certificate key in PEM format ./domain.crt
$ ? Enable multi-user mode No
$ ? Do you want to set up an email service? No
$ ? A name for your server (not required, but will be presented on your server’s frontpage) [return]
$ ? A description of your server (not required)[return]
$ ? A logo that represents you, your brand, or your server (not required)[return]
$ config created on <… …>/node-solid-server/build/config.json
- …/bin/solid-test start
After registration, remember add your user name before localhost, e.g.
if your user name is test.
The popup will return unauthorized err if the address is only
https://localhost:8443/. The issue also happens in multi-user mode and cannot be fixed by the method mentioned above.
If anyone is familiar with solid authentication, would you plz explain the mechanism? I don’t see it implemented in WAC way coz I set them all foaf:agent.