Skip to main content

UpdateProjectGatewayProject

PATCH 

/admin/v1/project-gateways/:id/projects/:project_id

Update a project's membership of a project gateway. The one mutable field is accepted_credentials, which says whether an Agent Router API key, a verified IdP token, or either one authenticates a caller of this project on this gateway. A new attachment starts at ACCEPTED_CREDENTIALS_API_KEY, which is what every project did before the field existed.

TOKEN and BOTH declare that the project accepts a credential verified at this gateway, so both are refused with FAILED_PRECONDITION while nothing on this gateway verifies the project's tokens. An enabled jwt gateway auth policy of the project's own verifies them, and so does a claim-to-project binding that names the project on an enabled jwt policy of this gateway. Removing the last of these, by disabling or deleting the policy or deleting the binding, is refused while the membership declares either one. Both are Enterprise-only, refused with FAILED_PRECONDITION on SaaS the way a jwt gateway auth policy is.

A project that only a binding verifies is admitted on a token call that names it in x-tars-project only when the token carries the value of one of that policy's bindings for the project. A data plane older than 0.13.0 refuses such a call with issuer_not_accepted, and admits only the calls that name no project.

The data plane enforces the declaration from release 0.7.0: it refuses an IdP token on a project declaring API_KEY, and an API key on a project declaring TOKEN. A data plane older than 0.7.0 authenticates API keys alone, whatever the declaration says.

Returns NOT_FOUND when the project is not attached to this gateway.

Request​

Responses​

Success