Authorization for Blobs/Objects

Is your feature request related to a problem? Please describe.

Add the ability set specific users to be able to read and/or write certain files via required login.

Describe the solution you'd like
Make use of the work on

• #1733

To allow the blob endpoint (objects) to be readable and/or writable by specific user lists/accounts.

Would like to see a role(s) added to support managing these user groups.

Ideally the blobs could also be in groups as well so that this does not require a 1 to many relation ship and could be many to many.

I.e.

Object group / blobs
forecasting-reports

• forecast.txt
• forecast.dss
• forecast.json
• etc

Users List
Forecast Users

• bob@bob.com
• sally@sally.com

Object group can map to User List

forecast-reports <-> Forecast Users
or
forecast.txt -> Forecast Users
or
forecast-reports <- bob@bob.com

Describe alternatives you've considered
Add files to S3 directly or place them in the public dir in our repo. Currently all blobs are listable.

Should this be worked on now, or wait and be done with the authorization work?

Additional context
Users currently place files places on the site and benefit from lack of discovery for unlisted content.

Start by reviewing issue #1733 and the blob/object endpoint authorization work. Define how required login, read/write permissions, roles, and user or object groups should map before implementation. Done means specific users or groups can be granted read and/or write access to blobs while access and listing behavior are covered.