Support Kerberos Ticket Cache for trino authentication#17080
Support Kerberos Ticket Cache for trino authentication#17080vjain143 wants to merge 1 commit intotrinodb:masterfrom
Conversation
|
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
Praveen2112
left a comment
Praveen2112
left a comment
There was a problem hiding this comment.
Thanks for working on this. Can we have some test coverage for this PR. We could have a PTs Environment with credentialCache and config test for KerberosConfig . We did something similar for hive connector and we could apply similar restriction here ref : #13482
| this.keyCache = keyCache; | ||
| return this; | ||
| } | ||
|
|
There was a problem hiding this comment.
Can we apply some sort of a validation here so that we could either keyTab or credentialCache but not both, like how we do in hive connector.
|
Yeah, It's hard to have test setup for this. But I will look into this. |
|
We do have PT Environment where we test kerberized hive - we could have another environment with credential cache |
|
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua |
|
👋 @vjain143 @Praveen2112 - this PR has become inactive. If you're still interested in working on it, please let us know. We're working on closing out old and inactive PRs, so if you're too busy or this has too many merge conflicts to be worth picking back up, we'll be making another pass to close it out in a few weeks. |
|
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua |
|
Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time. |
3 participants
Description
This pr is new feature for trino authentication using kerberos credential cache, trino only support key tab file based authentication , which if not support in large enterprises.
Additional context and related issues
Release notes
( ) One new property is introduce - 'http-server.authentication.krb5.keycache'