feat(HTTPSend): Add OAuth 2.0 and Bearer Token options

[ianshade]

About the Contributor

This PR is opened on behalf of TV 2 Norge,

Type of Contribution

This is a:

Feature

Current Behavior

Unless handled completely outside of the TSR, requests made through HTTPSend can't be authorized.

New Behavior

Two authorization methods are supported in the HTTPSend integration:

• OAuth 2.0 Client Credentials Flow: when configured, credentials are exchanged for a Bearer token that is added to EVERY outgoing request made through this instance of HTTPSend, and automatically refreshed.
• Long-lived Bearer token that is added to EVERY outgoing request. (probably not that common, but can be useful for testing purposes)

Testing Instructions

Other Information

Status

• PR is ready to be reviewed.
• The functionality has been tested by the author.
• Relevant unit tests has been added / updated.
• Relevant documentation (code comments, system documentation) has been added / updated.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 3.22581% with 60 lines in your changes missing coverage. Please review.

Project coverage is 37.36%. Comparing base (c782645) to head (76592f2).

Files	Patch %	Lines
...tegrations/httpSend/AuthenticatedHTTPSendDevice.ts	0.00%	59 Missing ⚠️
...ges/timeline-state-resolver/src/service/devices.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##           release50     #329      +/-   ##
=============================================
- Coverage      37.58%   37.36%   -0.22%     
=============================================
  Files            106      107       +1     
  Lines          10247    10306      +59     
  Branches        2452     2511      +59     
=============================================
  Hits            3851     3851              
- Misses          6395     6454      +59     
  Partials           1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jstarpl]

I think it would be useful to specify that this is the "base URL" of the oauth flow, i.e. the way the "token host" is described in the simple-oauth2: "Base URL used to obtain access tokens". I don't think "token host" is a widely used term in the OAuth world. Also, specifying that this is in fact a URL (and not, say a hostname + path) would be helpful.

[ianshade]

I made changes to the UI descriptions of this setting, and I added another field to allow specifying the path

[jstarpl]

Hello!

Thank you for contributing to the Sofie Project!

If you haven’t already, please give our contribution guidelines a read. I have found a a single usability-related issue, with the term "token host" that I would argue should be called something that contains a URL to specify that this is in fact a base URL for the OAauth flow. Once that's addressed, it should be merged within a few days.

[jstarpl]

Since release50 is feature-frozen and this is a new feature, I'll redirect this PR towards release51.