@kapa.ai how can I create a custom source that authenticates with a JWT token added as a query parameter?

The knowledge sources explain how to configure JWT authentication in both the Connector Builder UI and in config-based YAML, but they only describe sending the JWT in the

Authorization

header, not as a query parameter. [JWT auth (Builder); JWT auth (YAML)] They do not explicitly document a way to: 1. Generate a JWT with

JwtAuthenticator

, and 2. Inject that generated token into the request query string instead of the

Authorization

header. Because of that, I can’t confidently give you a fully supported, documented pattern for “JWT in query param” based only on these sources. What is documented: • You can configure JWT auth (secret key, algorithm, headers, payload, token duration, etc.) so Airbyte generates a signed token. [JWT auth (Builder); JwtAuthenticator schema] • The documented behavior is that this token is sent in the

Authorization

header with a configurable prefix (e.g.

Bearer

). [JWT auth (Builder)] What’s missing: • There is no example or option in the docs showing how to take that generated JWT and place it into a query parameter (e.g. `?token=`jwt). Given these limitations, the safest conclusion based on the docs is: • Airbyte supports JWT generation via

JwtAuthenticator

and the Connector Builder’s JWT method, but the official documentation does not describe a way to attach that JWT as a query parameter instead of an

Authorization

header. If you need this behavior, you’ll likely have to: • Either adjust the target API to accept

Authorization

headers, or • Ask in the Airbyte Slack / forums whether there is an undocumented pattern (e.g., using a more advanced declarative YAML setup) to reuse the generated JWT in query params, since it’s not covered in the current docs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

hi @Iosu Miral hope you are good. Were you able to overcome this? thanks so much!!

Hi, no, in the end I took a different route using python directly, sorry

ah... ok. thank you!!