You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An idea from today's planning meeting: today, we will expect users to generate their collector credentials via a CLI tool. Another approach that would work would be to expect the Collector to generate & store these credentials, and use Divvi Up's API to communicate these credentials.
Some thoughts:
Initial implementation could be by the already-existing API tokens -- this would work today, but requires the person configuring the Collector to provide this one token. An easier flow may be possible via OAuth, but this would require implementation work.
Ideally, this would be something we could document well enough that non-DU-authored Collectors could use the flow, too.
The text was updated successfully, but these errors were encountered:
An idea from today's planning meeting: today, we will expect users to generate their collector credentials via a CLI tool. Another approach that would work would be to expect the Collector to generate & store these credentials, and use Divvi Up's API to communicate these credentials.
Some thoughts:
The text was updated successfully, but these errors were encountered: