Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

base kmsauth token on bastion_user instead of remote_usernames #58

Merged
merged 5 commits into from
Jun 8, 2017
Merged

base kmsauth token on bastion_user instead of remote_usernames #58

merged 5 commits into from
Jun 8, 2017

Commits on Apr 30, 2017

  1. base kmsauth token on bastion_user instead of remote_usernames

    @djcrabhat
    djcrabhat committed Apr 30, 2017
    Configuration menu
    Copy the full SHA
    073fdb4 View commit details
    Browse the repository at this point in the history

Commits on May 7, 2017

  1. enforce that bastion_user == remote_usernames by default. add config … 

    …to allow different remote_usernames
    @djcrabhat
    djcrabhat committed May 7, 2017
    Configuration menu
    Copy the full SHA
    b3e4eab View commit details
    Browse the repository at this point in the history

  2. add tests for allowing remote_usernames to differ

    @djcrabhat
    djcrabhat committed May 7, 2017
    Configuration menu
    Copy the full SHA
    7e8f30f View commit details
    Browse the repository at this point in the history

  3. eek out some test coverage

    @djcrabhat
    djcrabhat committed May 7, 2017
    Configuration menu
    Copy the full SHA
    5b02087 View commit details
    Browse the repository at this point in the history

  4. make sure all requested remote_usernames are allowed to be used 

    added positive test mocking kmsauth sucessfully decrypting a token
    @djcrabhat
    djcrabhat committed May 7, 2017
    Configuration menu
    Copy the full SHA
    c9e1e02 View commit details
    Browse the repository at this point in the history