Tips about NSS

Esamina le note relative a config.json, .db/oidc/users/*.json e all'impostazione cors-proxy. Individua la posizione appropriata della documentazione nel repository, quindi pubblica lì le indicazioni sull'amministrazione di NSS e sul self-hosting, mantenendo gli esempi e rendendo chiare le indicazioni su URL-encoding.

I have been experimenting with NSS for use with the Data Kitchen project and I'm going to use this space to record some notes which may be of use to NSS system admins and also those self hosting NSS. If this belongs somewhere else, please just move it or suggest a better place to post it.

Directly examining/editing user accounts

Look in the folder where your config.json points the database (by default .db). There should be files in .db/oidc/users/*.json. There is one file per user which should contain plain text of the their username, email and other account info as well as a hash of their password.

Using the Cors Proxy

In config.json, set cors-proxy to a URI in your document root e.g. /proxy

You can now use https://yourNSS/proxy?uri=https://example.com/foo (note : the URI should be URL-encoded). This can be used directly in a client even if going to https://example.com/foo without the proxy is forbidden by Cors rules. This lets your request to https://example.com.foo be sent by the server rather than directly sent from the client.