Skip to content

add SESSION_AUTHORIZATION to client capabilities #551

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

kempspo
Copy link

@kempspo kempspo commented Apr 14, 2025

Description

PR seeks to resolve issue #545.

Trino expects the Client Capabilities header SESSION_AUTHORIZATION exists so that it allows the SET SESSION AUTHORIZATION.

This wasn't added in the initial PR

Non-technical explanation

Release notes

( ) This is not user-visible or docs only and no release notes are required.
(x) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

* Fix `SET SESSION AUTHORIZATION` not working. ({issue}`545`)

@cla-bot cla-bot bot added the cla-signed label Apr 14, 2025
@kempspo kempspo requested a review from hashhar April 14, 2025 14:20
Copy link
Member

@hashhar hashhar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I'll make some changes and merge - namely adding constants for the capabilities header value since it ideally should be exactly the same everywhere in the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants