Allow non-owners to access a shared resource with a web app of their own choice about authorization-panel HOT 6 OPEN

@elf-pavlik does this more or less capture what you described during today's community call?

from authorization-panel.

cc @zenomt

from authorization-panel.

Can we transfer this issue to app-authorization-panel repo?

from authorization-panel.

Thank you @michielbdejong I does indeed! In general I think that ACL should only stay responsible for giving permissions to agents. Agents need to stay responsible for managing their trust for apps.
I will also follow up with you in solid/web-access-control-spec#34

from authorization-panel.

Without this feature, sharing a resource could feel like how sharing an office document worked in the 90's: you could only view the documents you receive if you used the same app as the sender, if you used a different app, you had to email back and forth asking them to export/convert the document.

I cannot emphasize this strongly enough.

Solid promises app/data independence. Being too strict with app restrictions breaks that promise.

We need better mechanisms for specifying which apps can access data. For instance, things like:

• I trust all apps that have received a certification from parties A, B, or C

Suggestion: can we turn this issue into a PR with a set of use cases?

from authorization-panel.

I'll make PR with one or two use cases where person gives some global trust to specific app. Maybe you can make PR with use case for that:

I trust all apps that have received a certification from parties A, B, or C

?

from authorization-panel.