Bug #97735 | ALTER USER IF EXISTS ... WITH_MAX_USER_CONNECTIONS 9999 not applied correctly | ||
---|---|---|---|
Submitted: | 21 Nov 2019 15:46 | Modified: | 4 Feb 2020 17:35 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Security: Privileges | Severity: | S3 (Non-critical) |
Version: | 5.7.27, 5.7.28 | OS: | Any (CentOS 7) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ALTER USER |
[21 Nov 2019 15:46]
Simon Mudd
[21 Nov 2019 17:26]
Simon Mudd
A follow on comment. I was looking at https://dev.mysql.com/doc/refman/8.0/en/alter-user.html to double check intended behaviour and notice no reference in this document to "when" the changes apply and what happens to existing connections. So clarifying what happens to existing connections for a user when ALTER USER is executed would be good, as well as what happens to new users after the ALTER USER has been executed. Again I was looking at 5.7 and am not sure if 8.0 behaves differently, but ideally we'd like "user changes" to be visible as soon as possible after they are executed for existing connected users.
[22 Nov 2019 8:45]
MySQL Verification Team
Hello Simon, Thank you for the report. Observed reported behavior with 5.7.28 build. regards, Umesh
[22 Nov 2019 8:46]
MySQL Verification Team
Test results - 5.7.28
Attachment: 97735_5.7.28.results (application/octet-stream, text), 6.34 KiB.
[4 Feb 2020 17:35]
Paul DuBois
Posted by developer: Fixed in 5.7.30, 8.0.20. Using ALTER USER to reset an account MAX_USER_CONNECTIONS value did not take effect until all current account connections terminated, if there were any.