POC for hardcoded frontend/backend user mapping [DO NOT MERGE] #4284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit is just a POC! It hardcodes the mapping of frontend to backend usernames. Client can connect to ProxySQL with frontend credentials (username and password) and in case of successful authentication it will replace username with the mapped username. It will later retrieve the password using the backend username. The mapping (and also the client authentication) will fail if the mapped username doesn't exist, or if the password of the mapped username is not in clear text. Because the mapped password must be in clear text, variable `admin-hash_passwords` must be set to `false`. Attributes like `default_hostgroup`, `default_schema`, and `transaction_persistent` are all retrieved from the frontend user entry. Mapping is not supported for ``COM_CHANGE_USER()` executed by client.
|
retest this please |
renecannao
changed the title
|
retest this please |
|
Can one of the admins verify this patch? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit is just a POC!
It hardcodes the mapping of frontend to backend usernames. Client can connect to ProxySQL with frontend credentials (username and password) and in case of successful authentication it will replace username with the mapped username. It will later retrieve the password using the backend username.
The mapping (and also the client authentication) will fail if the mapped username doesn't exist, or if the password of the mapped username is not in clear text.
Because the mapped password must be in clear text, variable
admin-hash_passwordsmust be set tofalse.Attributes like
default_hostgroup,default_schema, andtransaction_persistentare all retrieved from the frontend user entry.Mapping is not supported for
COM_CHANGE_USER()executed by client.