-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
fix(wip): Changes to support presto impersionation with ldap #13156
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13156 +/- ##
==========================================
+ Coverage 53.06% 58.42% +5.36%
==========================================
Files 489 468 -21
Lines 17314 15920 -1394
Branches 4482 4088 -394
==========================================
+ Hits 9187 9301 +114
+ Misses 8127 6619 -1508
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@rijojoseph07 Which release is this targeted for? I am having issues with Impersonation on SSv1.0.1 |
@villebro Can you please help here? |
@rijojoseph07 how can I help? This PR appears to be closed. |
I meant if you have any details on the release date, can you please share it? @villebro |
1.1 has been cut many weeks ago and is approaching the first RC (@betodealmeida might know a more exact timeline), but I'd need to know which PR you are interested in seeing included. |
@DRavikanth was asking for a targeted release for this PR since he is facing issues with impersonation. |
@rijojoseph07 AFAIK this PR isn't merged, so it's not in master or any upcoming release, either. If you wish to have this PR reviewed, please reopen it. |
Sorry @villebro I got confused with this PR which was merged. #13214 |
Ok, now I understand; #13214 is included in the upcoming 1.1 version, so shouldn't be long now 🙂 |
Thanks, @villebro. @DRavikanth FYI ^^ |
SUMMARY
Fix for issue #11359, #9406
When using LDAP authentication with presto/trino, the current behavior is just to modify the URL to replace the username which will result in an unauthorized exception. This PR will fix this by updating the connection argument with the effective user.
TEST PLAN
Step 1: Setup database connection to presto without credentials in URL.
Step 2: Provide admin(who can impersonate as any other user in presto) credentials in connection properties via extras
Step 3: Enable impersonation for the database connection.
Step 4: Log in with a different user and run the query via SQL lab and you will see the principal user as admin and user as the logged-in user in presto UI.
ADDITIONAL INFORMATION