Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Header info didn't have x_token_server #484

Closed
1 task done
JonMerlevede opened this issue Sep 13, 2024 · 1 comment
Closed
1 task done

Header info didn't have x_token_server #484

JonMerlevede opened this issue Sep 13, 2024 · 1 comment

Comments

@JonMerlevede
Copy link
Contributor

Expected behavior

When using OAuth authentication and posting an access token that is no longer valid but can be refreshed, the Trino Python client refreshes the token without requiring user interaction.

Actual behavior

When using OAuth authentication and posting an access token that is no longer valid but that can be refreshed, the Trino Python client crashes with the exception:

trino.exceptions.TrinoAuthError: Error: header info didn't have x_token_server

Steps To Reproduce

  • Obtain an access token from Trino through the OAuth flow, and let Trino save it to your keyring.
  • Wait until the access token expires, but not so long that the token can no longer be refreshed.
  • Make another call to Trino.

This issue has also been reported in the trino dbt client: starburstdata/dbt-trino#432.

Log output

No response

Operating System

Mac

Trino Python client version

0.329.0

Trino Server version

443-e.7

Python version

Python 3.10.3

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants