Skip to content

No test scenario for 403 PERMISSION_DENIED #92

Description

@hdamker

Problem description
code/API_definitions/kyc-tenure.yaml's info.description documents that a 403 PERMISSION_DENIED error is returned when the access token doesn't have the required scope:

If the API consumer has a valid access token that does not have the required scope to obtain tenure information for the specified network subscription, then a 403 PERMISSION_DENIED error is returned.

The checkTenure operation also wires '403': $ref: '#/components/responses/Generic403'. code/Test_definitions/kyc-tenure.feature has no scenario covering this response — the Generic-400 and Generic-401 sections aren't followed by a Generic-403 one.

Expected action
Add a scenario for the documented insufficient-scope case, consistent with the existing Generic 400/401 error sections.

Additional context
None.

Activity

  1. added a commit that references this issue on Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions