Summary
How to handle session token path when the session ID is stored in the body for an Airbyte connector
Question
In Airbyte I want to create an connector using an session token. I get the session token in the initial response, but can’t extract the value. The issue is that an session token path is mandatory, but the session Id is stored in the body. I want to leave the field empty, but that field is mandatory. How to fix this?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["create-connector", "session-token", "mandatory-field", "session-id", "fix-issue"]
Did you already configure the authentication process under Global configuration
?
Should be there, here a screenshot of one of my connectors:
Yes. That one works, because I get the correct token in the body. Tried leaving the field blank in the YAML with . I get an error that the JWT token is disformed.
do you see the token value being sent in the request? I’m curious what it’s matching
I think that match is using Dpath under the hood, but I’m not sure there’s a way to match the body string correctly in that context
Yes. It’s strange that the field is mandatory, when the response is placed directly in the body. There is no wildcard i can use?
no, with dpath *
expands nested. I suppose maybe .
could match, but I’m not sure it would even be allowed in this context.
I’m a bit surprised that a RESTful API is returning the token like this, since it isn’t a JSON response
I wonder if the API has a return type option for the auth endpoint that changes that output
It’ s not an JSON reponse, but application/x-www-form-urlencoded. Tried to change to json, but then i get an authentication error.