MySQL Bugs: #58938: not able to add user account

Bug #58938	not able to add user account
Submitted:	15 Dec 2010 6:31	Modified:	19 Dec 2010 18:17
Reporter:	Sidney van de Stouwe	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.31 CE	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	account, user

Description:
Not able to add a user account
did run mysql_update and all was reported ok.

How to repeat:
Start a new configuration with only root account
Start workbench and try to add user --> error adding account

Suggested fix:
add user on mysql command line
after adding user one is able to change users particulars as required
not sure if this is a workbench or a server issue

What exact version of MySQL Workbench, 5.x.y, do you use?

I'm using the latest version: 5.2.31 CE of the Workbench

I am having the same problem using 5.2.31.  Even with no priveleges I get "Unhandled Exception:  Error adding account user@%".

I am having the same problem as soon as I upgraded to the latest version. I am doing this on a new/clean MySQL install.

Hi,

I had this problem on 5.5.7 and now on 5.5.8.  When I click 'Apply' to add a new account I get the message 'Unhandled Exception: Error adding account xxxxx@xxx'.

I tracked it down to being caused by the query that Workbench uses to insert a new user into the mysql.user table not providing a default value for the new authentication_string field.  I turned strict mode off and I was able to create a user successfully.

This is obviously just a workaround, so it appears that the query does need amending.  I'm just surprised this hasn't affected more users.

Regards

Rob

Workbench related issue

Bug #59024 was marked as a duplicate of this one.

Verified with 5.2.31 on Mac OS X while working with server version 5.5.8. This is what we can see from the error message:

Unhandled exception: Error adding account user2@%: Error executing 'Field 'authentication_string' doesn't have a default value'
INSERT INTO mysql.user (User, Host, Password, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv, Create_view_priv, Show_view_priv, Create_routine_priv, Alter_routine_priv, Create_user_priv, Event_priv, Trigger_priv, Create_tablespace_priv, max_questions, max_updates, max_connections, max_user_connections, ssl_cipher, x509_issuer, x509_subject) VALUES ('user2', '%', '', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 0, 0, 0, 0, '', '', '').
SQL Error: 1364

Since 5.5.7 new NOT NULL column was added to this table:

...
  `authentication_string` text COLLATE utf8_bin NOT NULL,
...

and Workbench "does not know" about this, while using direct INSERTs instead of CREATE USER + GRANT statements. If server runs in strict mode for all tables, the INSERT above fails.

Duplicate of bug #59000

I had this same symptom using WB 5.2.13 with db 5.5.9 .  I used Rob Gardener's workaround successfully (thanks, Rob!).

I have worked around this problem by INSERT'ing a record directly into mysql.user, like this. After this, I can edit the user through the Workbench-application, like intended.

I still have the same issue on MySQL Workbench 6.3 CE.

While creating an Account (Add Account/User) , it gives "Error Saving Account" , Error creating account @%;Operation CREATE USER failed for 'xyz'@'%'.

I copied wb_admin_security_be.py to C:\Program Files\MySQL\MySQL Workbench 6.3 CE\ folder as mentioned above. But not a success. 

am I missing anything?