From fce87aa6022c86f24786a822c8ba2299ae7fa482 Mon Sep 17 00:00:00 2001 From: PEDRO DIEZ GARCIA Date: Tue, 31 Mar 2026 08:39:41 +0200 Subject: [PATCH] Refactor Invalid Token Context Error --- artifacts/CAMARA_common.yaml | 2 +- documentation/CAMARA-API-Design-Guide.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/artifacts/CAMARA_common.yaml b/artifacts/CAMARA_common.yaml index 2bf87fd1..3fe766a4 100644 --- a/artifacts/CAMARA_common.yaml +++ b/artifacts/CAMARA_common.yaml @@ -387,7 +387,7 @@ components: status: 403 code: INVALID_TOKEN_CONTEXT # message: "{{field}} is not consistent with access token." - message: "... is not consistent with access token." + message: "Request body is not consistent with access token." # GENERIC_403_{{SPECIFIC_CODE}}: # description: Indicate a Business Logic condition that forbids a process not attached to a specific field in the context of the API # value: diff --git a/documentation/CAMARA-API-Design-Guide.md b/documentation/CAMARA-API-Design-Guide.md index 805d21ba..b9ff2b7c 100644 --- a/documentation/CAMARA-API-Design-Guide.md +++ b/documentation/CAMARA-API-Design-Guide.md @@ -410,7 +410,7 @@ In the following, we elaborate on the existing client and server errors. In part | 400 | `{{SPECIFIC_CODE}}` | `{{SPECIFIC_CODE_MESSAGE}}` | Specific Syntax Exception regarding a field that is relevant in the context of the API (e.g. format of an amount) | | 400 | `OUT_OF_RANGE` | Client specified an invalid range. | Specific Syntax Exception used when a given field has a pre-defined range or a invalid filter criteria combination is requested | | 403 | `PERMISSION_DENIED` | Client does not have sufficient permissions to perform this action. | OAuth2 token access does not have the required scope or when the user fails operational security | -| 403 | `INVALID_TOKEN_CONTEXT` | `{{field}}` is not consistent with access token. | Reflect some inconsistency between information in some field of the API and the related OAuth2 Token. This error SHOULD be used only when the scope of the API allows it to explicitly confirm whether or not the supplied identity matches that bound to the Three-Legged Access Token. | +| 403 | `INVALID_TOKEN_CONTEXT` | Request body is not consistent with access token. | Reflect some inconsistency between information in some field of the API and the related OAuth2 Token. This error SHOULD be used only when the scope of the API allows it to explicitly confirm whether or not the supplied identity matches that bound to the Three-Legged Access Token. | | 409 | `ABORTED` | Resource is being modified by another operation. Please wait, and retry if appropriate. | The resource is undergoing modification by another process | | 409 | `ALREADY_EXISTS` | The resource that a client tried to create already exists. | Trying to create an existing resource | | 409 | `CONFLICT` | A specified resource duplicate entry found. | Duplication of an existing resource (**This Error Code is DEPRECATED**) |