Allowing Jerakia to authenticate with our Vault

AppRole authentication is the recommended method of authenticating with Vault.

When using this authentication method, Jerakia is configured with a role ID (role_id) and a secret ID (secret_id), and Jerakia uses these values to acquire a limited-lifetime token from Vault to interact with the API of the transit backend. 

Upon token expiry, Jerakia will request a new token using role_id and secret_id again.

First, we'll create an AppRole for Jerakia, giving it a TTL of 15 minutes. This has to be associated with the access policy we created earlier using the policies argument:

$ ./vault write auth/approle/role/jerakia token_ttl=15m policies=jerakia

Now, we can check the Jerakia AppRole and ascertain ...

Get Mastering Puppet 5 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.