Simplify generating API keys for gateways

[KrishnaIyer]

Summary

Simplify generating API keys for gateways

Current Situation

We have the API Key screen today to create a gateway API key.

Why do we need this? Who uses it, and when?

API Keys for gateways can only be one of two types

1. Gateway connection (including LBS LNS): This API key requires only one right Right_RIGHT_GATEWAY_LINK, "link as Gateway to a Gateway Server for traffic exchange, i.e. write uplink and read downlink"
2. CUPS: This requires three rights:
   • View Gateway Information
   • Retrieve Secrets Associated with the gateway
   • Edit basic gateway settings

Instead of users going to this page and selecting the rights, we should make this easier.

Proposed Implementation

In the overview page of a particular gateway, have a button to generate an API Key.

• Here we can provide a dropdown with two types (connection/LNS and CUPS) and an optional expiry.
• Once the user selects it we either have the same "please copy the key" or we can generate a file and auto download via the browser.

Contributing

• [ ] I can help by doing more research.
• [ ] I can help by implementing the feature after the proposal above is approved.
• [X] I can help by testing the feature before it's released.

Code of Conduct

• [X] I agree to follow TTN's Community Code of Conduct.

[KrishnaIyer]

Phase 3 of https://github.com/TheThingsIndustries/product-management/issues/29

[KrishnaIyer]

@pierrephz: This is also a good one for you to work on the UX for.

@mjamescompton for the implementation.