0be49a97b7
vault: stopExpiration should be idempotent
2015-04-14 13:32:56 -07:00
a360ca4928
logical/framework: AuthRenew callback, add LeaseExtend
...
/cc @armon - Going with this "standard library" of callbacks approach
to make extending leases in a customizable way easy. See the docs/tests
above.
2015-04-11 14:46:09 -07:00
992028e23e
vault: the expiration time should be relative to the issue time
2015-04-10 21:21:06 -07:00
b10fbc4d83
vault: Adding token based revocation
2015-04-10 14:48:08 -07:00
98679ee7b8
vault: Split expiration manager views to index by token
2015-04-10 14:21:23 -07:00
13836e8612
vault: groundwork to allow auth renew
2015-04-10 13:59:49 -07:00
e7fe48c33f
vault: refactor expiration timer management
2015-04-09 12:39:12 -07:00
5a3ab973e6
vault: Simplify common lease logic
2015-04-09 12:29:13 -07:00
7df486482b
vault: Adding LeaseIssue for renew to allow limiting maximum lease length
2015-04-09 11:54:32 -07:00
82c5d9c478
vault: Enforce non-renewability
2015-04-08 17:03:46 -07:00
512b3d7afd
vault: Adding metrics profiling
2015-04-08 16:43:17 -07:00
429ad7e5cb
vault: Handle auth entry without lease
2015-04-08 15:43:26 -07:00
466c7575d3
Replace VaultID with LeaseID for terminology simplification
2015-04-08 13:35:32 -07:00
493ee49e4d
vault: unify the token renew response
2015-04-06 16:35:39 -07:00
adaa83b48c
vault: Adding RenewToken to expiration manager
2015-04-03 11:58:10 -07:00
c82fbbb8c3
vault: Support prefix based token revocation
2015-04-03 11:40:08 -07:00
1b19a8ee1b
vault: Rename RegisterLogin to RegisterAuth
2015-04-02 17:45:42 -07:00
08a9216aa7
vault: register vault ID even fi no lease
2015-03-31 21:04:10 -07:00
2c9ebecda7
vault: register zero lease entries with the expiration manager
...
/cc @armon - would appreciate a review on this one
2015-03-31 21:01:12 -07:00
69593cde56
remove credential/ lots of tests faililng
2015-03-30 18:07:05 -07:00
65ef4f1032
vault: wire tokens into expiration manager
2015-03-23 18:11:15 -07:00
86c9bd9083
vault: Give expiration manager a token store reference
2015-03-23 18:00:14 -07:00
539554fc0b
vault: only log expiration notice if useful
2015-03-23 17:27:46 -07:00
c349e97168
vault: clean up VaultID duplications, make secret responses clearer
...
/cc @armon - This is a reasonably major refactor that I think cleans up
a lot of the logic with secrets in responses. The reason for the
refactor is that while implementing Renew/Revoke in logical/framework I
found the existing API to be really awkward to work with.
Primarily, we needed a way to send down internal data for Vault core to
store since not all the data you need to revoke a key is always sent
down to the user (for example the user than AWS key belongs to).
At first, I was doing this manually in logical/framework with
req.Storage, but this is going to be such a common event that I think
its something core should assist with. Additionally, I think the added
context for secrets will be useful in the future when we have a Vault
API for returning orphaned out keys: we can also return the internal
data that might help an operator.
So this leads me to this refactor. I've removed most of the fields in
`logical.Response` and replaced it with a single `*Secret` pointer. If
this is non-nil, then the response represents a secret. The Secret
struct encapsulates all the lease info and such.
It also has some fields on it that are only populated at _request_ time
for Revoke/Renew operations. There is precedent for this sort of
behavior in the Go stdlib where http.Request/http.Response have fields
that differ based on client/server. I copied this style.
All core unit tests pass. The APIs fail for obvious reasons but I'll fix
that up in the next commit.
2015-03-19 23:11:42 +01:00
8039fc5c63
logical/framework: support renew
2015-03-19 20:20:57 +01:00
d4b284fba4
logical/framework: revoke support
2015-03-19 19:41:41 +01:00
061b6b24f1
vault: Refactor to use CollectKeys
2015-03-18 12:06:18 -07:00
46ccb81db4
vault: Respect grace period for revocation
2015-03-16 17:09:18 -07:00
e52f1ee960
vault: Testing sys/renew
2015-03-16 16:11:55 -07:00
5f1e3e5986
vault: Testing restore
2015-03-16 15:11:47 -07:00
703bcd8190
vault: Testing revoke and renew
2015-03-16 15:11:47 -07:00
e85cd66b30
all: Removing fields from Lease
2015-03-16 13:29:51 -07:00
18069d4cf7
vault: Handle a negetive renew increment
2015-03-16 11:52:38 -07:00
bdfa320e01
vault: First pass at expiration manager
2015-03-16 11:35:43 -07:00
12b12e578c
vault: fix merge conflict + pass tests
2015-03-15 19:38:23 -07:00
ca358f64dd
vault: Merge conflict
2015-03-15 18:06:19 -07:00
b96ac9f95f
vault: Assign renew time
2015-03-15 18:05:31 -07:00
d1d1929192
vault: convert to logical.Request and friends
2015-03-15 14:53:41 -07:00
63a9eb321a
logical: put structs here, vault uses them
2015-03-15 14:27:06 -07:00
9d5db1286d
vault: Track the renew time
2015-03-13 11:36:24 -07:00
f0d00e77ec
vault: Adding start/stop to expiration manager
2015-03-13 11:31:43 -07:00
d744d4ee5e
vault: integrate expiration manager with core setup/teardown
2015-03-13 11:20:36 -07:00
5ce63ea7cd
vault: Adding lease registration
2015-03-13 10:56:03 -07:00
e77ce26d31
vault: spec out expiration manager API
2015-03-12 18:38:22 -07:00
15de847389
vault: Setup expiration manager on unseal
2015-03-12 12:44:30 -07:00
Armon Dadgar