You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
App passwords, in a sense, are like API keys for the "normal" user - they allow access to a resource without sharing the main account password. Frequently, at least in my usecase, app passwords are used for single-purpose software or situations (for example, a task-list or calendar client app).
I'd like to propose that app passwords be assigned granular permissions, which would allow one to set up, for example, a calendar app which can only access your calendar, instead of everything on the server.
Starting out, it could be as simple as:
One blanket permission for each app (one for calendar, one for tasks, etc) - perhaps breakout read and write?
File reading
File writing/modification
Account Administration/Ability to Log in (as opposed to WebDAV access)
As such, an example permission list on a typical NextCloud instance might look like:
App: Calendar
App: Tasks
App: Notes
File Read
File Write and Modification
Log-in
The text was updated successfully, but these errors were encountered:
App passwords, in a sense, are like API keys for the "normal" user - they allow access to a resource without sharing the main account password. Frequently, at least in my usecase, app passwords are used for single-purpose software or situations (for example, a task-list or calendar client app).
I'd like to propose that app passwords be assigned granular permissions, which would allow one to set up, for example, a calendar app which can only access your calendar, instead of everything on the server.
Starting out, it could be as simple as:
As such, an example permission list on a typical NextCloud instance might look like:
The text was updated successfully, but these errors were encountered: