Single-sign-on vs siloed access

Posted Feb 15, 2019 15:01 UTC (Fri) by Flameeyes (guest, #51238)
Parent article: Some challenges for GNOME online accounts

I haven't really looked into GOA for years, but isn't one of the problem with the single-sign-on that the user needs to provide permissions for the full set of capabilities of all apps?

That doesn't sound like a particularly positive feature to me, even without Flatpak: why would my email client use the same permission as a document browse? What if I want two different apps to have access to a cloud storage but for different folders, that never should be mixed together?

Single-sign-on vs siloed access

Posted Feb 16, 2019 20:00 UTC (Sat) by smcv (subscriber, #53363) [Link]

> isn't one of the problem with the single-sign-on that the user needs to provide permissions for the full set of capabilities of all apps?

That's why GOA isn't intended to be used in apps outside GNOME itself (although that wasn't always communicated very well in the past, and there's no technical mechanism to stop unsandboxed third-party apps from using it).