keys table structure

[anonymoussprocket]

Column	Data Type	Description
keyid	numeric, primary key	sequence auto-increment pk
key	text, not null	32-char API key
resourceid	numeric	FK reference to resources table
userid	numeric	FK reference to users table
tierid	numeric	FK reference to tiers table
dateissued	timestamp	date from which the key is active
datesuspended	timestamp	a means of terminating a key

[vishakh]

What keys are these? How are they used?

[anonymoussprocket]

These are API keys that the REST services require in the headers.

[vishakh]

Could we change the table name to api_keys?

[ivanopagano]

Should a single user have multiple keys for each tier he has access to?
Will this imply that the user can somehow manage his keys?

[anonymoussprocket]

Say no to snake case.

Single user will have multiple keys as they are resource-specific. Your API key for the dev tezos node will not be the same as your API key for prod Conseil instance.

The user can't directly manage keys except to request they be re-issued. Keys are auto-generated by the system.