[REQUEST]: Gracefully Handle 403 Response From Non-essential Endpoints

[mlm483]

Description

In DeltaBreed, our Experimental Collaborator role has read access to a specific set of experiments they are invited to collaborate on. They do not have access to germplasm endpoints (such as /search/germplasm) and they must not be able access pedigree information or germplasm list information.

Field Book makes calls to the /brapi/v2/germplasm endpoint, which returns a 403 Forbidden response if the authenticated user is an Experimental Collaborator when using Field Book with DeltaBreed.

It seems like all of the essential features of Field Book could operate without the data from that endpoint, the /brapi/v1/observationunits endpoint already returns germplasmName, for example. If Field Book continued to function without results from /brapi/v2/germplasm (even if some features or data in the app are absent or limited), that would support our use case.

Alternatives

We will test with returning empty responses instead of 403 Forbidden, it is unknown how Field Book will handle this (attempted) workaround.

Additional Context

No response