MySQL Bugs: #92333: Wildcards wrongly disallowed in limit to hosts matching

Bug #92333	Wildcards wrongly disallowed in limit to hosts matching
Submitted:	7 Sep 2018 7:44	Modified:	7 Sep 2018 13:07
Reporter:	Cedric Counotte	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	8.0, 8.0.12, 8.0.33	OS:	Windows (10)
Assigned to:		CPU Architecture:	Any

Description:
It's not possible to enter any hosts match like this:
   host_begin%host_end

When doing so, the workbench shows a white cross in a red disc and says (lol):
   % and _ wildcards may be used

Nevertheless, applying such config shows an error message:
   Invalid host specification
   The host specification "...%..." is not valid

BUT, in msql command line it just works fine.

How to repeat:
Try to enter a 'limit to hosts matching' in a user login configuration, such as: host_begin%host_end

It shows an error icon with an ok message and it fails to apply.

Suggested fix:
Show a ok icon and make apply succeed as it should.

Hello Cedric,

Thank you for the report.
Observed this on Win7 with WB 8.0.12.

regards,
Umesh

Problem persists with WorkBench 8.0.14 running on Windows 10 64 bit.

this is also the case when entering an ipv6 address like fe80::9415:debf:a0b:c043%12 (even without the numbers behind the percent). It is possible to create this account using a statement, but it cannot be altered via Workbench.

This is still not fixed in 8.0.33. When using the MySQL Workbench GUI to enter the LIMIT TO HOSTS MATCHING FIELD our FQDN it is obviously too long for the field and as soon as we enter the 37th character the GUI freezes and we have no option but to crash out of the Workbench. We have had to use the IP Address instead but this is not best practice

Bug #112563 marked as duplicate of this one.