App Center should rely on saved login credentials to perform snap management actions.
Opened this issue · 1 comments
Is there an existing issue for this?
- I have searched the existing issues and found none matching what I'm reporting.
Is the feature related to a problem or existing issue?
No response
Describe the feature, why the feature matters to you, and what benefits the feature will bring about.
Users have the option of logging in via a console to authenticate with snapd and the credentials being saved to ~/.snap/auth.json. This allows a user to perform privileged actions like installing, refreshing, or removing snaps without having to reauthenticate via a polkit prompt or using sudo. A user need not login again as long as the auth.json file is present.
The App Center should use the saved snapd credentials of the logged-in user to perform snap management actions to avoid authorization prompts.
Describe any alternatives you've considered.
No response
Additional context
From the "snap help login" help text:
The login command authenticates the user to snapd and the snap store, and saves
credentials into the ~/.snap/auth.json file. Further communication with snapd
will then be made using those credentials.
This text seems to suggest that once upon a time the snap store did use the saved login credentials. In which case, can that functionality be restored to the App Center?
Thank you for the report! This would bring the App Center inline with the convenience of the CLI.
Having the App Center respect the ~/.snap/auth.json is one change. We'd also want to surface the ability to log in to the user in the App Center, which will need UI/UX input.