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

vault: honor new token_period in vault token role #6574

Merged
merged 2 commits into from
Oct 29, 2019
Merged

vault: honor new token_period in vault token role #6574

merged 2 commits into from
Oct 29, 2019

Commits on Oct 28, 2019

  1. vault: Support new role field token_role 

    Vault 1.2.0 deprecated `period` field in favor of `token_period` in auth
role:

>  * Token store roles use new, common token fields for the values
>    that overlap with other auth backends. `period`, `explicit_max_ttl`, and
>    `bound_cidrs` will continue to work, with priority being given to the
>    `token_` prefixed versions of those parameters. They will also be returned
>    when doing a read on the role if they were used to provide values initially;
>    however, in Vault 1.4 if `period` or `explicit_max_ttl` is zero they will no
>    longer be returned. (`explicit_max_ttl` was already not returned if empty.)
https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#120-july-30th-2019
    Mahmood Ali committed Oct 28, 2019
    Configuration menu
    Copy the full SHA
    321fd41 View commit details
    Browse the repository at this point in the history

  2. Test with Vault latest, 1.2.3 

    To ensure we test with latest with latest configuration.
    Mahmood Ali committed Oct 28, 2019
    Configuration menu
    Copy the full SHA
    008ae5b View commit details
    Browse the repository at this point in the history