Auth API UI

Goal: Implement the proposed UI for the new Auth API.

Links:

• Auth API project
• Invision project
• Auth API reference

Auth API Keys pages must provide the UI to the new Auth API Top levels operations are:

• Regenerating the master key.
• Edit the public key settings.
• Create, regenerate and delete regular keys.

As you can check in the attached Invision project, there are two main forms:

• API keys list. First key is the master key, the second one is the public key and then the regular ones.
• API key settings page: this form has two differents ways of presenting the information:
  • For the public key: you can change APIs access and dataset Read access. Notice that there’s only read access for this kind of key.
  • For the regular ones: you can set APIs access and CRUD operations for each dataset. These keys can’t be edited.

NOTES:

• There’s neither Import nor Analysis API even though they’re present in the mockup.
• The link icon copies the key to the clipboard.
• Now this page must get all the user datasets. It’s not clear what happens with shared datasets so far so let’s begin getting only your own datasets.

[javitonino]

We should probably remove this: Learn more about using your simple API key in CARTO from the bottom of the page. Maybe replace it for a link to the new docs. For sure, remove that simple now that our api keys rock 🎸

[inigomedina]

If there is no action, we shouldn’t use any verb. Your solution, in that case, looks good. However, if there is some kind of action, but not one so specific like edit or configure, we could just go for a generic one like Manage your API key.