9 Commits

Author	SHA1	Message	Date
vishalnayak	72b0390c9e	Added renewal capability to app-id backend	2016-02-24 10:40:15 -05:00
Jeff Mitchell	45e32756ea	WriteOperation -> UpdateOperation	2016-01-08 13:03:03 -05:00
Jeff Mitchell	51e948c8fc	Implement the cubbyhole backend ... In order to implement this efficiently, I have introduced the concept of "singleton" backends -- currently, 'sys' and 'cubbyhole'. There isn't much reason to allow sys to be mounted at multiple places, and there isn't much reason you'd need multiple per-token storage areas. By restricting it to just one, I can store that particular mount instead of iterating through them in order to call the appropriate revoke function. Additionally, because revocation on the backend needs to be triggered by the token store, the token store's salt is kept in the router and client tokens going to the cubbyhole backend are double-salted by the router. This allows the token store to drive when revocation happens using its salted tokens.	2015-09-15 13:50:37 -04:00
Armon Dadgar	5151516127	cred/app-id: testing upgrade to salted keys	2015-06-30 18:37:10 -07:00
Armon Dadgar	ae324ce941	cred/app-id: first pass at automatic upgrading to salting	2015-06-30 18:09:08 -07:00
Jonathan Sokolowski	a4f9bacb28	credential/app-id: Test DeleteOperation	2015-05-14 22:30:02 +10:00
Mitchell Hashimoto	51093d3d18	credential/app-id: allow restriction by CIDR block [GH-10]	2015-04-17 10:14:39 -07:00
Mitchell Hashimoto	ddd678bf48	credential/app-id: support associating a name with app ID [GH-9]	2015-04-17 10:01:03 -07:00
Mitchell Hashimoto	61b7b71dec	credential/app-id	2015-04-04 18:41:49 -07:00