Required Role not handled well when getting content

Description

When setting the role that must be assigned to content in order for it to be returned in API calls, it must be assigned to only the "Read" privilege.

For example, the default required role is "Content Api Access." Content needs to have the "Read" privilege of that role. If you add other privileges (e.g., Create or Publish), calling the API to get data from that content returns 404 not found error.