Option for Session Token (Authorization) ApiKey Request Option Format (Enabling Baserow)

[mattsah]

Airbyte offers a lot of flexibility for creating custom API connectors. Unfortunately, API developers don't always follow best practices. In this case, Baserow, a popular no-code database/form/application builder, uses a rather "custom" mechanism for Authenticating. Specifically:

• They use the Authorization header and require a token obtained via a distinct request.
• While Session Token Retrieval gets us 90% of the way there, the problem arises when trying to establish how that token should be sent.
• Bearer is insufficient, because "Bearer" is not how they specify the Authorization type.
• ApiKey is insufficient, because they still require a prefix, e.g. Authorization: JWT <token>

Providing a "format" option as an additional (optionally) defined field on the ApiKey request option would enable more complete customization of any header values sent. If empty, the token itself could just be sent (making this a non-breaking change). Example:

Beneath the "Header Name" at the bottom a field named "Format" could be added with some info on how to use such that someone could enter a value which is then interpolated to include the token, enabling custom "Authorization" headers.

Format:
[ JWT {{ authorization["token"] }} ]