Skip to content

branch-4.1: [enhance](nereids) improve masking of user's password for ALTER USER and CREATE USER commands in audit logs #62141#63038

Open
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-62141-branch-4.1
Open

branch-4.1: [enhance](nereids) improve masking of user's password for ALTER USER and CREATE USER commands in audit logs #62141#63038
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-62141-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 6, 2026

Cherry-picked from #62141

…and CREATE USER commands in audit logs (#62141)

### What problem does this PR solve?

This PR adds masking for users passwords for **CREATE USER** and **ALTER
USER** commands.
The masked values will be stored in audit table and audit files instead
of actual values.
The same functionality already exists for **SET USER PASSWORD** and
**SET LDAP_ADMIN_PASSWORD** commands, so we other commands related to
passwords should be masked as well.

**Could you please include this PR into 4.x branches, please!**

Issue Number: close #62140
@github-actions github-actions Bot requested a review from yiguolei as a code owner May 6, 2026 16:16
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@yiguolei
Copy link
Copy Markdown
Contributor

yiguolei commented May 7, 2026

run buildall

@iaorekhov-1980
Copy link
Copy Markdown
Contributor

hello, @yiguolei
Could you please provide output of failed FE_UT test?
Is it something serious or just flaky test?
Because original PR has successfully passed FE_UT in #62141

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants