You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there are 2 ways to implement Kerberos support:
Introduce a new option custom_auth in Client constructor opts for a custom authorization header string. When present, it will set authorization header as specified somewhere near here in the code. Developers must find their own way to generate the authorization header (for Kerberos it means using other libraries like kerberos or krb5.)
Introduce an optional dependency kerberos and support kerberos authentication similar to PyHive's.
Personally I prefer 1 because it introduces less code change on the library. If this is preferred, I can submit a pull request on this :)
The text was updated successfully, but these errors were encountered:
I am trying to connect to a Trino server guarded with Kerberos authentication.
Currently the authorization header is designated here, in HTTP basic auth: https://github.com/tagomoris/presto-client-node/blob/master/lib/presto-client/index.js#L98
I think there are 2 ways to implement Kerberos support:
custom_auth
inClient
constructoropts
for a custom authorization header string. When present, it will set authorization header as specified somewhere near here in the code. Developers must find their own way to generate the authorization header (for Kerberos it means using other libraries like kerberos or krb5.)kerberos
and support kerberos authentication similar to PyHive's.Personally I prefer 1 because it introduces less code change on the library. If this is preferred, I can submit a pull request on this :)
The text was updated successfully, but these errors were encountered: