Sha256: 8bd5b910fa8af3039e4e1a44be3d14e49bce90244af4868307cd350eefd78e4c
Contents?: true
Size: 1.01 KB
Versions: 15
Compression:
Stored size: 1.01 KB
Contents
Feature: Keys
In Order to restrict access to repositories
As Gritano
I want to manage user's keys
Background:
Given the following users exist:
| login |
| igorbonadio |
| jessicaeto |
Scenario Outline: Add user key
Given I add "<key>" key to "<user>"
When I generate the authorized_keys
Then I should see "<authorized_keys>" authorized_keys
Examples:
| user | key | authorized_keys |
| igorbonadio | igorbonadio.pub | igorbonadio_authorized_keys |
| jessicaeto | jessicaeto.pub | jessicaeto_authorized_keys |
Scenario: Generate autorized_keys
Given I add "igorbonadio.pub" key to "igorbonadio"
And I add "jessicaeto.pub" key to "jessicaeto"
When I generate the authorized_keys
Then I should see "full_authorized_keys" authorized_keys
Scenario: Duplicated keys
Given I add "igorbonadio.pub" key to "igorbonadio"
When I add "igorbonadio.pub" key to "igorbonadio"
Then I should see that "igorbonadio" has only one key
Version data entries
15 entries across 15 versions & 1 rubygems