authentication.feature

@endpoint(authentication) @endpoint(authentication-v1)
Feature: Authentication
  All requests to Datadog’s API must be authenticated. Requests that write
  data require reporting access and require an `API key`. Requests that read
  data require full access and also require an `application key`.  **Note:**
  All Datadog API clients are configured by default to consume Datadog US
  site APIs. If you are on the Datadog EU site, set the environment variable
  `DATADOG_HOST` to `https://api.datadoghq.eu` or override this value
  directly when creating your client.  [Manage your account’s API and
  application keys](https://app.datadoghq.com/organization-settings/) in
  Datadog, and see the [API and Application Keys
  page](https://docs.datadoghq.com/account_management/api-app-keys/) in the
  documentation.

  Background:
    Given an instance of "Authentication" API
    And new "Validate" request

  @skip-validation @team:DataDog/credential-management
  Scenario: Validate API key returns "Forbidden" response
    When the request is sent
    Then the response status is 403 OK

  @team:DataDog/credential-management
  Scenario: Validate API key returns "OK" response
    Given a valid "apiKeyAuth" key in the system
    When the request is sent
    Then the response status is 200 OK
    And the response "valid" is equal to true