[Feature request] Multiple admin-secret keys and secret key management

Currently, Hasura only allows 1 secret key as admin role.

This feature request suggests a tab on console for admin to add/edit/revoke more key-role pair:

• Key is the access_key
• Role is the role.
• (optional) Expired time (default is forever)

So, this will allow bypass JWT authentication for specific client.

The default admin-secret should be immutable and showable for the first admin only.

API usage:

Client needs to send header x-hasura-secret-key to access hasura.

Use case:

• I have some 3rd party applications which needs a key to access hasura.
• A team could safely colloborate in console with many roles: dev, database administrators, manager,… with each role has only specific permissions.

Related issue:

https://github.com/hasura/graphql-engine/issues/587

With this feature, hasura will eventually support access console for all roles.

Alternative solution:

We need a table secret_keys with three columns above and a join table between secret_keys and the table you want to grant access. And use secret_keys in permissions settings.

[mnlbox]

@revskill10 I love your idea Or maybe more general if Hasura can support a simple user password authentication and merge that with jwt or webhook then admin users can use builtin authentication feature. (I think this approach is more dynamic than key/role approach and still we can use one specific user/password rather than key/password for specific client app)

In that case we also need some new permissions for example called:

• access_data_tab
• access_graphql_tab
• access_remote_schema_tab
• access_trigger_tab

To restrict access to each part of console app.

[jasonmccallister]

@revskill10 are you thinking more along the lines of allowing multiple admins specific keys to hit the API or console? I think that would be really useful as people leave teams/companies then you only need to remove that users admin key.