Code of Conduct: https://github.com/solid/process/blob/main/code-of-conduct.md - Website: https://solidproject.org
github-actions[bot] on gh-pages
deploy: 4f620aea3e91daf5ce9591d… (compare)
github-actions[bot] on gh-pages
deploy: 4d6bfbb95b42fac67edcabe… (compare)
timea-solid on main
Update FormsReadme.md (compare)
timea-solid on main
Form documentation (#502) * do… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
timea-solid on formDocumentation
Update Documentation/FormsReadm… (compare)
import { getSolidDataset, saveSolidDatasetAt } from "@inrupt/solid-client";
so my stupid question, how can I use JSON-LD to get Data and save data in JSON-LD format? thanks a lot for your help
0
, which means that the client doesn't expire — where as ESS expires clients after a certain amount of time (configurable)
["authorization_code", "refresh_token"]
Hi, i have a question: I'd like to authenticate to a (REST) API endpoint(s) (written with express.js) with a Solid identity. (Sort of like we authenticate to solid data pods with Solid identity all the time, but instead of data pod it's a custom API). Is there a library to take care of that, server-side?
I've briefly tried out @solid/access-token-verifier (not successful, yet) and maybe somebody knows if it's the right choice and perhaps even has some tips or examples how to use it?
(i also looked at express-openid-connect, but it seems to expect a fixed issuerBaseURL
, which doesn't work in Solid context with many issuers, otherwise it would be a perfect fit)
In other words, we send an authenticated fetch request from our app to the API endpoint (perhaps using @inrupt/solid-client-authn-browser). The API receives the request.
Now, it should look at the authorization
header, do the necessary talking with identity provider, or whatever business it needs to do, and tell us that it's a valid token and return the requester's webId, and clientId, or throw error otherwise.
We need a library that does the part written in italics. If it's already wrapped as express middleware, even better.
Thank you!
I'd like to use it for solid index. It's a little server, you give it a uri, it looks at it and saves relationships (triples) it's interested in (into mysql database). Then others can find you and your things via these relationships, using a ldf server on top of the database.
I have it working (without auth) at https://index.ditup.org/inbox, the indexed data can be queried at https://index.ditup.org/ldf, and it's all used by https://solid.ditup.org (all in early stages of development).
solid:storage
was indeed one I used (as a basis for then adding things to solid:publicTypeIndex
and/or solid:privateTypeIndex
), and the fact that its presence apparently also can't be relied on (https://forum.solidproject.org/t/data-discovery-on-community-solid-server/4695/9) kinda was the final straw that caused me to give up on further app development for now. So looking forward to your work :)
Following along here but I don't understand this bit:
"If you sign as yourself on your own pod, you already have control because pod owners automatically have control..."
Isn't that what I'm doing every time I sign into any app? In other words, any app I sign in as has full control over my pod?