Is your feature request related to a problem? Please describe.
Recently, I had to release a patch with new credentials from DWAB because the previous ones expired. Since client credentials are embedded into the executable, all releases before v1.8.1 no longer work as of June 4th, 2024. I don't want people using outdated versions of the switcher, but that is better addressed by something like #34 than incidentally gating releases to fail at the end of the season.
Describe the solution you'd like
Develop an auth server on top of DWAB's system, which can more easily handle dynamically swapping secrets.
- This may be a good use case for Cloudflare Workers
- Grant a private key/client secret for each released version to communicate with the auth server. The auth server can then retrieve bearer tokens on the individual client's behalf
- Slight security improvements
Describe alternatives you've considered
Continue to our current behavior.
- Releases will no longer work at the end of the season, and there is not a clear indication why
- The current approach is a lot simpler, with fewer failure modes
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Recently, I had to release a patch with new credentials from DWAB because the previous ones expired. Since client credentials are embedded into the executable, all releases before
v1.8.1no longer work as of June 4th, 2024. I don't want people using outdated versions of the switcher, but that is better addressed by something like #34 than incidentally gating releases to fail at the end of the season.Describe the solution you'd like
Develop an auth server on top of DWAB's system, which can more easily handle dynamically swapping secrets.
Describe alternatives you've considered
Continue to our current behavior.
Additional context
Add any other context or screenshots about the feature request here.