Error message 'Jwt issuer is not configured'

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Error message ‘Jwt issuer is not configured’ causing issues with access token renewal


Question

Hi all!

Am I the only one that, for the past hour, received error {"message":"Jwt issuer is not configured," "code":401}?

Everything worked well, from my development app to the testing inside the documentation, but now nothing works.

The error seems to come from the access token (which, as per the documentation, I renew at each request)


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

["error-message", "jwt-issuer-not-configured", "access-token", "documentation"]
2

I’m getting the same error. I just created an application following the tutorial https://reference.airbyte.com/reference/authentication|here. The access token I get either from UI or the endpoint (https://reference.airbyte.com/reference/createaccesstoken) is not working and throwing 401.

3

Seems like it’s fixed. It’s working properly for me. https://github.com/airbytehq/airbyte/discussions/44487

4

On cloud for me too.

It’s seems fix today!