raghav-reglobe commented on PR #66115: URL: https://github.com/apache/doris/pull/66115#issuecomment-6789462807
@CalvinKirs thanks for the review and the approval. Agreed — today both clauses fall back to the existing ALTER USER / SET PASSWORD FOR gate (global GRANT_PRIV), which keeps the MySQL intent (it gates them behind APPLICATION_PASSWORD_ADMIN even on one's own account, so a briefly known password cannot be parked in the secondary slot) but is coarser than it, since Doris has no finer privilege for "manage my own secondary password". For the follow-up I see two shapes: a dedicated privilege for the clauses (the closest to MySQL), or allowing them on one's own account when the statement proves the current password (MySQL's REPLACE '<current>' / PASSWORD REQUIRE CURRENT). I'll open an issue to settle which once this lands. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
