example-https-file.jsonconfig there where you can replace the paths pointing to the https key/cert
/profileand perhaps some others) to a FileDataAccessor that uses
/ServerRootas root folder instead of what was passed with the
-fparameter. https://gist.github.com/joachimvh/da75e1239fb026db0b3375ded505b21f contains a similar example I made showing how regex routing can work. A bit more config would then also be needed to have FileDataAccessor point at a fixed folder instead of the default one. I can provide a config example if you want to go into that direction. Not sure if it covers everything you want
example-https-file.jsonbut pass that one on the start-command ? see https://forum.solidproject.org/t/make-css-multi-user-mode-first-get-ssl-running/4624 I'm sure I will come up with more questions once it is time... for example how do I make a service unit possible to run 24/7...
example-https-file.json(or create a custom copy of it somewhere) and pass that one to the
config/identity/email/default.jsonyou could also remove that import from your config (you'll see it in the list of imports) and instead copy your changes into the body of your config (just so you're not dependent on editting files in the CSS project itself)
[Unit] Description=Solid - Social Linked Data Documentation=https://github.com/solid/community-server After=network.target [Service] Type=simple User=root ExecStart=/usr/lib/node_modules/@solid/community-server/bin/server.js -c @css:file.json -b https://solidweb.me/ Restart=on-failure [Install] WantedBy=multi-user.target
communityss.service - Solid - Social Linked Data Loaded: loaded (/lib/systemd/system/communityss.service; enabled) Active: active (running) since Tue 2021-08-31 15:35:15 CEST; 117ms ago Docs: https://github.com/solid/community-server Main PID: 14025 (node) CGroup: /system.slice/communityss.service └─14025 node /usr/lib/node_modules/@solid/community-server/bin/server.js -c @css:file....
@elf-pavlik To give you an overview, the OIDC/IDP component was originally written by Jackson and Matthieu, with a lot of the heavy lifting being done by the node-oidc-provider library. Afterwards I have made several changes based on issues and extra features. So if a new feature needs to be added it would probably be done by me, but my OIDC knowledge is mostly based on the issues I encountered and conversations I had with @matthieubosquet so is definitely not comprehensive.
I can join such a meeting though, just not sure what level of OIDC spec knowledge is required to have a valuable discussion :D