Allow all read-only endpoints for custom macaroons #456
Description
Is your feature request related to a problem? Please describe.
We now have the ability to create custom sessions with macaroons that only allow users to access specific URIs. However, when a macaroon is created with limited permissions (like only being able to access loop or pool) the terminal-web interface becomes unusable.
Every page has many error messages pop up because requests are being made to URIs that the user does not have permission to view.
Describe the solution you'd like
It would be helpful if there was an option when creating a custom macaroon to allow all "read-only" endpoints in addition to the custom URIs desired.
Describe alternatives you've considered
It is currently possible to work around this issue by making a list of all the "read-only" endpoints and including them with every custom macaroon created by the UI. The drawback for this method is that whenever new read-only endpoints are added, all custom macaroons would need to be recreated to include the new endpoint.