Feature: Handle current users collection of keys

  LEAP currently uses OpenPGP and is working on implementing katzenpost.
  Both systems require public keys of a user to be available for retrival.

  The /2/keys endpoint allows the client to manage the public keys
  registered for their users email address.

  You need to specify the type of the key when publishing it. Some
  keytypes such as 'openpgp' and 'katzenpost_id' will only allow a
  single key to be published. Others such as 'katzenpost_link' allow
  multiple keys to be registered at the same time. We deal with this
  by allowing arbitrary json data to be specified as the value of the
  key. So katzenpost_link keys can be combined in a json data structure.

  POST request will register a new key. In order to replace an existing
  key you need to send a PATCH request to /keys/:type including the last
  revision (rev) of the key. This way we can detect conflicts between
  concurrend updates.

  Background:
    Given I authenticated
    Given I set headers:
      | Accept       | application/json |
      | Content-Type | application/json |
      | Authorization | Token token="MY_AUTH_TOKEN" |

  Scenario: Get initial empty set of keys
    When I send a GET request to "2/keys"
    Then the response status should be "200"
    And the response should be:
    """
      {}
    """

  Scenario: Get all the keys
    Given I have published a "openpgp" key
    And I have published "katzenpost_link" keys
    When I send a GET request to "2/keys"
    Then the response status should be "200"
    And the response should be:
    """
    {
    "openpgp": {
      "type": "openpgp",
      "value": "DUMMY_KEY",
      "rev": "DUMMY_REV"
      },
    "katzenpost_link": {
      "type": "katzenpost_link",
      "value": {
        "one": "DUMMY_KEY",
        "two": "DUMMY_KEY"
      },
      "rev": "DUMMY_REV"
      }
    }
    """

  Scenario: Get a single key
    Given I have published a "openpgp" key
    When I send a GET request to "2/keys/openpgp"
    Then the response status should be "200"
    And the response should be:
    """
    {
      "type": "openpgp",
      "value": "DUMMY_KEY",
      "rev": "DUMMY_REV"
    }
    """

  Scenario: Get a set of keys for one type
    Given I have published "katzenpost_link" keys
    When I send a GET request to "2/keys/katzenpost_link"
    Then the response status should be "200"
    And the response should be:
    """
      {
        "type": "katzenpost_link",
        "value": {
          "one": "DUMMY_KEY",
          "two": "DUMMY_KEY"
          },
        "rev": "DUMMY_REV"
      }
    """

  Scenario: Publish an initial OpenPGP key
    When I send a POST request to "2/keys" with the following:
    """
      {
      "type": "openpgp",
      "value": "ASDF"
      }
    """
    Then the response status should be "204"
    And I should have published a "openpgp" key

  Scenario: Do not overwrite an existing key
    Given I have published a "openpgp" key
    When I send a POST request to "2/keys" with the following:
    """
      {
      "type": "openpgp",
      "value": "QWER"
      }
    """
    Then the response status should be "422"
    And the response should be:
    """
      {
      "error": "key already exists"
      }
    """

  Scenario: Publishing an empty key fails
    When I send a POST request to "2/keys" with the following:
    """
      {}
    """
    Then the response status should be "422"
    And the response should be:
    """
      {
      "error": "param is missing or the value is empty: type"
      }
    """

  Scenario: Updating an existing key
    Given I have published a "openpgp" key
    When I send a PATCH request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "value": "QWER",
      "rev": "DUMMY_REV"
      }
    """
    Then the response status should be "204"
    And I should have published a "openpgp" key with value "QWER"

  Scenario: Updating a missing key raises
    When I send a PATCH request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "value": "QWER",
      "rev": "DUMMY_REV"
      }
    """
    Then the response status should be "404"
    And the response should be:
    """
      {
      "error": "no such key: openpgp"
      }
    """
    And I should not have published a "openpgp" key

  Scenario: Updating an existing key require revision
    Given I have published a "openpgp" key
    When I send a PATCH request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "value": "QWER"
      }
    """
    Then the response status should be "422"
    And the response should be:
    """
      {
      "error": "param is missing or the value is empty: rev"
      }
    """

  Scenario: Updating an existing key require right revision
    Given I have published a "openpgp" key
    When I send a PATCH request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "value": "QWER",
      "rev": "WRONG_REV"
      }
    """
    Then the response status should be "422"
    And the response should be:
    """
      {
      "error": "wrong revision: WRONG_REV"
      }
    """

  Scenario: Deleting an existing key
    Given I have published a "openpgp" key
    When I send a DELETE request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "rev": "DUMMY_REV"
      }
    """
    Then the response status should be "204"
    And I should not have published a "openpgp" key

  Scenario: Deleting a missing key raises
    When I send a DELETE request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "rev": "DUMMY_REV"
      }
    """
    Then the response status should be "404"
    And the response should be:
    """
      {
      "error": "no such key: openpgp"
      }
    """

  Scenario: Deleting an existing key require revision
    Given I have published a "openpgp" key
    When I send a DELETE request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp"
      }
    """
    Then the response status should be "422"
    And the response should be:
    """
      {
      "error": "param is missing or the value is empty: rev"
      }
    """
    And I should have published a "openpgp" key

  Scenario: Deleting an existing key require right revision
    Given I have published a "openpgp" key
    When I send a DELETE request to "2/keys/openpgp" with the following:
    """
      {
      "type": "openpgp",
      "rev": "WRONG_REV"
      }
    """
    Then the response status should be "422"
    And the response should be:
    """
      {
      "error": "wrong revision: WRONG_REV"
      }
    """
    And I should have published a "openpgp" key