Endpoint for claiming gateways using a qr code

[vlasebian]

Summary

References #7270

Changes

• Adding a grpc endpoint to claim gateways using a qr code
• Extending the qrcodegenerator pkg to support gateway qrs

Testing

curl -H "Authorization: $TTN_AUTH_TOKEN" 'http://localhost:1885/api/v3/qr-codes/gateways/ttigpro1/parse' -X POST -d '{"qr_code": "aHR0cHM6Ly90dGlnLnByby9jL2VjNjU2ZWZmZmUwMDAxMjgvYWJjZGVmMTIzNDU2"}'

where the qr_code field is the base64 encoded value of:

https://ttig.pro/c/ec656efffe000128/abcdef123456

or without specifying the format:

curl -H "Authorization: $TTN_AUTH_TOKEN" 'http://localhost:1885/api/v3/qr-codes/gateways/parse' -X POST -d '{"qr_code": "aHR0cHM6Ly90dGlnLnByby9jL2VjNjU2ZWZmZmUwMDAxMjgvYWJjZGVmMTIzNDU2"}'

Results

{"format_id":"ttigpro1","gateway_eui":"EC656EFFFE000128","owner_token":"abcdef123456"}

Regressions

None.

Notes for Reviewers

None.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[vlasebian]

What should be filled in for the rest of the ClaimGatewayRequest? The full request looks like this:

{
  "authenticated_identifiers": {
    "gateway_eui": "70B3D57ED000ABCD", // this is taken from the url
    "authentication_code": "string" // this is taken from the url too
  },
  "qr_code": "string", // if authenticated_identifiers are provided, this doesn't have to be filled in
  // how should the collaborator item be filled?
  "collaborator": {
    "organization_ids": {
      "organization_id": "string"
    },
    "user_ids": {
      "user_id": "string",
      "email": "string"
    }
  },
  // there is a comment for target_gateway_id in the protobuf message definition:
  // 'If this is not set, the target ID for the target gateway will be set 
  // to `<gateway-eui>`.' -> I guess this can be set to the gatewayEUI 
  "target_gateway_id": "string",
  "target_gateway_server_address": "string", // what value should we use for this? we let the user select it?
  // cups_redirection is deprecated
  "cups_redirection": {},
  // target_frequency_plan_id is deprecated
  "target_frequency_plan_id": "string",
  // what should we use for this?
  "target_frequency_plan_ids": [
    "string"
  ]
}

[johanstokking]

Looks pretty good. Please address lint errors and set up the linting tool in your editor.

[KrishnaIyer]

LGTM