nodeSolidServer / nodeSolidServer/node-solid-server
Development environments(solid-test) issues in single-user server
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
I installed the latest Solid-server.
Using a self-signed certificate.
$ ./bin/solid-test init
? Path to the folder you want to serve. Default is [mypath]/node-solid-server/data
? SSL port to run on. Default is 8443
? Solid server uri (with protocol, hostname and port) https://test.korea.ac.kr:8443
? Enable WebID authentication Yes
? Serve Solid on URL path /
? Path to the config directory (for example: /etc/solid-server) ./config
? Path to the config file (for example: ./config.json) ./config.json
? Path to the server metadata db directory (for users/apps etc) ./.db
? Path to the SSL private key in PEM format key.pem
? Path to the SSL certificate key in PEM format crt.pem
? 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) test.korea.ac.kr
? A description of your server (not required)
? A logo that represents you, your brand, or your server (not required)
config created on /home/jdh0139/test/solid/test1/node-solid-server/config.json
and run Solid-server
$ ./bin/solid-test start
Solid server (v5.4.0-1-g40544b2) running on https://localhost:8443/
Press <ctrl>+c to stop
(node:31090) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
Click Register in client to generate ID and PW.
And click Login.
An error occurred at this time.
Unauthorized
Please let me know if you did something wrong or if you have any actions to correct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with ./bin/solid-test init and ./bin/solid-test start using the shown self-signed certificate and single-user settings. Follow the Register and Login flow, then inspect the generated config.json and authentication behavior; done means login succeeds without returning Unauthorized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100