Alain Bourgeois

@jeff-zucker What is the problem ? I don't have any problem with https://bourgeoa.solidcommunity.net:8443 nor with https://bourgeoa.solidcommunity.net:8443/browse.html I tried with 2 different webId's : https://bourgeoa.solidcommunity.net:8443/profile/card#me and https://solidweb.me/bourgeoa/profile/card#me

The problem is that you are not logged out. You have the login button but you can edit your private file. @aveltens I'm wondering if it is the same problem...

@timbl @theRealImy Is this a very general question with solidos or rdflib to default fetch with `credentials: 'include'` https://developer.mozilla.org/fr/docs/Web/API/Request/credentials

@josephguillaume > When using the community solid server the NSS cookie is obviously never set so the login state is always correct. > > Instead, mashlib breaks for things like...

@josephguillaume Thanks. I also found this. https://www.twelve21.io/how-to-access-images-securely-with-oauth-2-0/#:%7E:text=4.%20USE%20SERVICE%20WORKERS @RubenVerborgh have you any idea to feed our discussion ? Is there a specification issue ?

> The solid:oidcIssuer field in WebIDs is now mandatory per https://solid.github.io/solid-oidc/#webid-profile (related to https://github.com/solid/node-solid-server/issues/1639 ) Thanks. It will be added. This is a very recent draft specification . Adding in...

As an alternate route and with the same idea that we have an `owner` stored in podRoot/.meta we could also reference oidcIssuer there and check any change in profile document...

Anyone with access to podRoot/.meta has full access to changing `owner` and taking control of the pod. Never give the key of your safe.

How do you change `servermanaged resource` ? They can only have Read access.

no need to implement for external webid in account creation lib/models/account-manager.js External WebId was removed from account creation https://github.com/solid/node-solid-server/pull/1566