Optionally change fitbit client-id and secret based on user-config

[nivemaham]

It would be great if the fitbit connector request could be configured based on user specific fitbit client configuration. This would allow us to have multiple fitbit clients at a time.

[yatharthranjan]

This will require updates to the rest-authorizer i assume ?

[nivemaham]

Yes. When we choose the client to authorize a user, we can persist it together and share it with connector.
Then the connector can use a user-config to get token and client config for requesting. Let's wait for @blootsvoets 's opinion.

[blootsvoets]

Yes, makes sense. So one table for API client credentials, and another table for users, that reference the ID of the client. We can use the fact that we already distinguish clients in the rest authoriser, we would just need a new dialog to create a new client. The rest connector would need to fetch credentials.

Example data structure:

clients:
  - id: 1
    name: RADAR Fitbit client
    type: Fitbit
    clientId: abc
    clientSecret: abc

users:
  - id: 1
    projectId: abc
    userId: abc
    clientId: 1
    ...