Open pmaier1 opened 7 years ago
👍 for oauth2
!!!
Guest user gets "Access to this resource is forbidden for guests."
now Instead of having the button "Authorize".
At this point I wonder if a blacklist wouldn't be preferable... It seems that in most cases we want users to be able to use everything, except some specific things, with the mindset of blocking instead of allowing ? (a bit like the firewall)
I think there was a reason for having a whitelist in the first way @butonic. In general I fully agree.
Related FR: https://github.com/owncloud/guests/issues/106
Regarding required code changes it is not a big deal changing from whitelist to blacklist. I don't have a preference here. It might be an issue when admins have to know/guess the correct apps names to blacklist unless #106 is implemented.
In any case we still need a list of apps (as stated in the OP), which never could be blacklisted.
If not checkboxes, there could be a label somewhere showing the list of apps that are accessible and not blacklisted. But yeah, checkboxes might be better there.
Moving to the next release and increasing priority.. Next release needs to have proper defaults!
We can provide default apps when nothing was set.
However if someone upgrades from an older version, we might need to write a migration that will automatically add the new defaults into the list.
My other suggestion was to make any app of type "authentication" to be always blacklisted. (oauth, impersonate, LDAP belong to that category)
moving to p3, leaving in milestone for now
moving to backlog for planning
Need to go through the whitelisted apps and specify the default settings. Current ones are not sufficient.
To add
To remove