615e209296
audit: Basic interface
2015-03-27 13:43:23 -07:00
2024c7a155
Fixing compilation errors due to API change
2015-03-24 16:20:05 -07:00
9a4946f115
vault: Testing core ACL enforcement
2015-03-24 15:55:27 -07:00
23864839bb
vault: testing root privilege restrictions
2015-03-24 15:52:07 -07:00
fe402cdd87
vault: ignore a nil policy object, as it has no permissions
2015-03-24 15:49:17 -07:00
b354f03cb2
vault: adding auth/token/lookup/ support
2015-03-24 15:39:33 -07:00
4a4d1d3e45
vault: adding auth/token/revoke/ and auth/token/revoke-orphan/
2015-03-24 15:30:09 -07:00
26f05f7a20
vault: Passthrough of client token to token store
2015-03-24 15:12:52 -07:00
6fd3cae2c2
vault: Adding auth/token/create endpoint
2015-03-24 15:10:46 -07:00
b5332404d1
vault: Allow providing token ID during creation
2015-03-24 14:22:50 -07:00
b41d2e6368
vault: utility string set methods
2015-03-24 13:56:07 -07:00
493fbc12fc
vault: utility string search methods
2015-03-24 13:44:47 -07:00
49df1570d6
vault: test missing and invalid tokens
2015-03-24 11:57:08 -07:00
20c2375352
vault: Adding ACL enforcement
2015-03-24 11:37:07 -07:00
43a99aec93
vault: Special case root policy
2015-03-24 11:27:21 -07:00
cb563b881c
logical: Special error for permission denied
2015-03-24 11:23:59 -07:00
4598e43140
vault: Adding ClientToken
2015-03-24 11:09:25 -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
6481ff9e34
vault: Generate a root token when initializing
2015-03-23 17:31:30 -07:00
cd3ee5cc03
vault: Remove core reference
2015-03-23 17:29:36 -07:00
539554fc0b
vault: only log expiration notice if useful
2015-03-23 17:27:46 -07:00
3607eae208
vault: Adding method to generate root token
2015-03-23 17:16:37 -07:00
f40ed182c4
vault: Support policy CRUD
2015-03-23 14:43:31 -07:00
192dcf7d39
vault: first pass at HandleLogin
2015-03-23 13:56:43 -07:00
879a0501f8
vault: Track the token store in core
2015-03-23 13:41:05 -07:00
56d99fe580
vault: token tracks generation path and meta data
2015-03-23 13:39:43 -07:00
2c42b8b364
credential: simplify interface
2015-03-23 13:39:16 -07:00
10e64d1e90
vault: extend router to handle login routing
2015-03-23 11:47:55 -07:00
af2fe5681a
main: hook up consul backend
2015-03-21 17:25:12 +01:00
3270349456
logical/consul: actual test that the token works
2015-03-21 17:23:44 +01:00
55a3423c60
logical/consul
2015-03-21 17:19:37 +01:00
27d33ad9f7
logical/framework: auto-extend leases if requested
2015-03-21 16:20:30 +01:00
05246433bb
logical/aws: refactor access key create to the secret file
2015-03-21 11:49:56 +01:00
665cbaa3e4
logical/aws: remove debug I was using to test rollback :)
2015-03-21 11:20:22 +01:00
9e4b9d593b
logical/aws: WAL entry for users, rollback
2015-03-21 11:18:46 +01:00
f6d5e3f0f4
logical/testing: immediate rollback, ignore RollbackMinAge
2015-03-21 11:18:33 +01:00
17c58633d6
logical/framework: rollback should return error, easier API
2015-03-21 11:08:13 +01:00
a54d90ac1f
logical/framework: rollback needs to have access to request for storage
2015-03-21 11:03:59 +01:00
a78b7207b9
vault: playing with credential store interface
2015-03-20 13:54:57 -07:00
82e13e3c41
vault: implement the sys/auth* endpoints
2015-03-20 12:48:19 -07:00
86a6062ba2
main: enable AWS backend
2015-03-20 19:32:18 +01:00
62d9bec8be
logical/aws
2015-03-20 19:03:20 +01:00
a0f59f682b
logical/framework: can specify InternalData for secret
2015-03-20 17:59:48 +01:00
d43f395050
logical/testing: rollback/revoke secrets, error dangling secrets
2015-03-20 17:20:55 +01:00
1ff229ca68
http: passing tests
2015-03-19 23:28:49 +01: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
7170bff4f9
vault: testing credential enable/disable
2015-03-19 10:39:47 -07:00
Armon Dadgar