Access to increased privileged data: 2 approaches

[nasajoey]

Some operational data have elements that are only accessible to those with increased privileges. There are at least two ways we can make this work.

1. Based on the scope presented to existing endpoints, the USS providing data ensures the correct data elements in the model are in the response. This increases complexity of request handling, but keeps the number of endpoints at their current level.
2. Have a parallel set of endpoints for enhanced requests. Makes each valid request receive the same data model and elements in response. This is at the cost of maintaining additional endpoints.

Would like to open conversation on this design choice. This is a brief description of the issue, happy to follow up with answers to any questions.

[boguwei]

Some operational data have elements that are only accessible to those with increased privileges.

Can you provide an example of this?

[nasajoey]

Sure.

In the current Position model hdop_gps isn't something that the PUBLIC would need to know, but may be helpful in some SAFETY related queries. Hence that data element is tagged with x-utm-data-accessibility: SAFETY

[boguwei]

Ah, thanks for the example.

Uber's preference is option 2. discussed so far, it seems the cost of maintaining additional endpoints is lower than the added complexity of filtering one set of endpoints on privilege.

[OrangeBean]

To add on @boguwei point: maintaining separate endpoints will allow mutate public and private models independently which might be required in the future.