Skip to content

Adjust privileges to make MySQL workbench work #2

@jan-meyer-1986

Description

@jan-meyer-1986
  1. I am not sure schema 'tmp' is there intentionally.
  2. It might be beneficial to slightly extend the privileges for guest account to allow:
    a) Dump of the databases with MySQL Workbench. This app requires more privileges than just SELECT. Unfortunately, many people might try to use this app and then write you about the privileges. For reference, I got:
    mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces mysqldump:
    Got error: 1044: Access denied for user 'guest'@'%' to database 'Ad' when using LOCK TABLES
    Unfortunately, I do not remember the names of all the required privileges, but I would start with 'LOCK TABLES' and 'SHOW VIEW'. For some schemas it might be enough, others might require more privileges → test it on all the schemas.
    b) Kill their own queries. Even a stupid select, which however uses a cross-join, can bring a db to the knees. Hence, consider granting 'PROCESS' privilege:
    'If you have the PROCESS privilege, you can see all threads. If you have the SUPER privilege, you can kill all threads and statements. Otherwise, you can see and kill only your own threads and statements.'

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions