2016.37

Bug Fixed

• In some cases, a GET /api/v1/users request incorrectly returned a 403 error.