Repository navigation
migration to CSS #62
Description
CSS has a file-system mode that could allow migration/mapping at the filesystem level.
This is a work in progress, to summarize some of the questions raised by solidcommunity.net migration/mapping from NSS to CSS
file system mapping
- resource mapping is using the same mapping convention : resource + contentType is mapped
- to file if file mimeType = contentType
- else to file$.ext with mimeType of ext = contentType
- profile is stored in card$.ttl
- .meta and .acl are turtle resources stored as files at the same relative location.
- pod mapping
- CSS a pod is allways stored in a folder named
user - while NSS pod data is stored in a folder named
subdomain
- CSS a pod is allways stored in a folder named
IdP
- authentication have different entry points (login) :
- CSS is using email as entryPoint versus WebId for NSS
- NSS may have multiple pod's with the same email, not CSS
solidcommunity.net on 20220603 has 59030 accounts but only 48445 emails
- idp migration
- data migration (?)
- or batch pod creation see issue Feat/seed accounts and pods CommunitySolidServer/CommunitySolidServer#1165
WebId structure
- NSS https://user.server/profile/card#me
- CSS can use subdomain configuration like NSS
or domain/user configuration https://server/user/profile/card#me
WebId profile
- in CSS extended profile (preferences) is not created by default : supported via custom pod templates (this is not a migration isssue)
- Resolved : NSS was missing
solid:oidcIssuerfor old pod's. see issue comment
and chat Resolved on current pod with https://github.com/RubenVerborgh/add-oidc-issuer
CSS functionalities
- CSS container as turtle do not display contentType by default
- v4 has it by default
- app authorisation
- CSS do not use the trustedApp mechanism.
- Note that this goes beyond the v0.9 spec; the mechanism is not secure and will not be supported in the default CSS configuration. However, no breakage occurs; the statements are simply ignored.
- NSS uses trustedApp at the pod or ACL document level
- CSS do not use the trustedApp mechanism.
- notifications ?
- CSS supports the unsecure Solid WebSockets API 0.1 in all versions up to and including v4.0.0, but the mechanism is scheduled to be removed from the default configuration in v5.0.0. (Note that this does conform to 0.9 since support is indicated as SHOULD, not MUST.) However, it will still be available as a custom module that can be plugged in, so keeping that functionality will not be an issue.
- owner implementation ? to allow unlock ACL Control : yes it does
mashlib issues
- mashlib can be linked to CSS has an external webApp
and CSS v3.0.0 has a recipe using mashlib by default - extended profile is not available in CSS missing properties are :
- space:storage
- solid:account
- preference files
- CSS domain is allways seen as a podStorage : pim:Storage is available on container representation even with no profile
Activity
elpoelma commentedon Mar 22, 2022
On the issues with mashlib
bourgeoa commentedon May 30, 2022
Top post edited with @RubenVerborgh responses
One new question : does CSS implement : "owner implementation ? to allow unlock ACL Control"
bourgeoa commentedon May 30, 2022
Thanks
bourgeoa commentedon Jun 4, 2022
as of 20220603 there are 59030 accounts but only 48445 emails
This covers 2 different situations : no email, or same email on multiple pods
timea-solid commentedon Jun 27, 2022
The plan I was tracking on this topic is:
First experiments with mashlib on CSS (reporting bugs)
Prioritize and fix high prio problems of SolidOS(mashlib) to be able to move to CSS
SolidOS team concerns about CSS
Working on checking/documenting Solid Apps working with CSS
Migrate Pods
Ongoing:
Done:
All tickets are monitored here: SolidOS team tasks & Git issues (view)
@timbl @justinwb @RubenVerborgh @bourgeoa @oolivo let's keep ourselves up to date with this ticket/comment. I will make sure to propagate this in SolidOS and Solid Team meetings to keep everyone (us and everyone else) informed.
bourgeoa commentedon Oct 11, 2022
timbl commentedon Nov 3, 2023
Now we have https://github.com/RubenVerborgh/NSS2CSS -- thanks to @RubenVerborgh -- I have checked off the box above "develop a migration script for data". I had understood originally that CSS and NSS used different password hash algorithms, and so a conversion from one to the other was impossible. But now it seems that was not in fact the case, and the conversion script is possible. That is a major step
timea-solid commentedon Oct 14, 2025
This task was concluded already. Can it be closed?
jeswr commentedon Oct 14, 2025
Closing!