MySQL Bugs: #50983: Not flushed privileges

Bug #50983	Not flushed privileges
Submitted:	8 Feb 2010 9:53	Modified:	26 Mar 2010 11:02
Reporter:	Alberto León	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2	OS:	Any (Vista, Ubuntu)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	flush, privileges

Description:
The checked privileges didn't flush. A connection for test an user created by admin - Workbench fail.

I test to assign privileges by console and all be ok.

How to repeat:
Add new user

Thank you for the problem report. Please, check with a newer version, 5.2.15, and inform about the results.

If you get the same behavior could you please describe step by step how you did?. Thanks in advance.

Yes, the bug is on 5.2.15b too.

Steps
1. Create new schema
2. Create new user and apply settings
3. Click on Schema Privileges
4. Select the new user
5. Add Entry
6. Selecte the new schema created
7. Click on "SELECT ALL"
8. Save changes
9. Go to Connections and add a new connection for this user
10. Test the connection (error throwed "acces denied to user 'nameUser'@'localhost')

HOW TO FIX
1. Go to console
2. GRANT ALL PRIVILEGIES .........
3. Go To Connections
4. Test it
5. And now you can do things

During configuring connection did you use "localhost" or "127.0.0.1" as hostname?

I try both

I tried both..., sorry I did grammar mistake in previous message

Verified as described by using Ubuntu.

looks like the problem lies within a not properly applied password for the user, rather than not properly flushed privileges. (at least thats what happened for me when trying to reproduce)

This has been fixed. The issue is actually that when an account is created, the password is not set.
If you re-set the password once the account is created, the problem doesnt appear.

Bug #51464 has been marked as duplicate of this one

this has been fixed in repository

An entry has been added to the 5.2.17 changelog:

In the Administrator section of MySQL Workbench, if a new user was created, the password was not correctly applied for the account, resulting in the new user being denied access when an attempt was made to connect to a server with that user account.