5 Commits

Author	SHA1	Message	Date
Dane Everitt	d03559080f	Theoretically fix migration issues for api_key table	2018-03-02 18:37:39 -06:00
Dane Everitt	d0bce4af97	Apply fixes from StyleCI (#875) ... [ci skip] [skip ci]	2018-01-14 12:07:14 -06:00
Dane Everitt	7aa540b895	Remove api permissions table	2018-01-14 12:05:18 -06:00
Dane Everitt	8e8147cc43	Apply fixes from StyleCI (#874) ... [ci skip] [skip ci]	2018-01-13 16:06:55 -06:00
Dane Everitt	e3df0738da	Change the way API keys are stored and validated; clarify API namespacing ... Previously, a single key was used to access the API, this has not changed in terms of what the user sees. However, API keys now use an identifier and token internally. The identifier is the first 16 characters of the key, and the token is the remaining 32. The token is stored encrypted at rest in the database and the identifier is used by the API middleware to grab that record and make a timing attack safe comparison.	2018-01-13 16:06:19 -06:00