No longer able to authenticate - "Jwt issuer is not configured" when testing API calls in reference

[pwlopez]

I was testing API calls via the reference and all of the sudden I can no longer authenticate and keep recieveing a code 401, "Jwt issuer is not configured".

[i0exception]

Same here!

[nataliekwong]

Hi there, are you using Cloud or OSS (Community or Enterprise)?

If Cloud or Enterprise, could you make sure to create a Support ticket if you have not already?

[assaadhjb]

Hi, Cloud for me, and Im running into the same issue...

[nataliekwong]

Hi @assaadhjb - we've investigated and discovered a fix, and this should be resolved now. Can you try again now?

If you are still having issues, please submit a Support ticket to our Support team to further triage.

[assaadhjb]

Still an issue 😕

After getting succesfully my-token from the request bellow:

curl --request POST \
     --url https://api.airbyte.com/v1/applications/token \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "client_id": "my_client_id",
  "client_secret": "my_client_Secret"
}'

I run

curl --request GET \
--url https://api.airbyte.com/v1/connections \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--header 'Authorization: Basic my-token'

This was working, until yesterday where I start receiving:

    "code": 401,
    "message": "Jwt is missing"
}

[nataliekwong]

Can you try this with a newly created application?

[timroes]

@assaadhjb Your Authorization header is wrong. It shouldn't be Basic <token>, but Bearer <token>. You're trying to initiate a HTTP Basic Auth (which we don't support).

Please let me know if you still seeing this issue after putting a Authorization: Bearer <token> header on your request.

[assaadhjb]

@nataliekwong @timroes thanks both. Now it's working!
Sorry, Idk if it relates to Cloud users as well, but I think the Basic auth in the doc for OSS users is a bit confusing

[timroes]

@assaadhjb Thank you for the feedback. This document is indeed outdated and state the old state before we build authentication in Airbyte onto the new system. I'll make sure we're adopting this to reflect the correct current solution.

[josephkmh]

The docs have been updated, thanks for the feedback @assaadhjb!