obtaining the actor that is sending the request, and authorization evaluates whether the actor has permission to make the request. Vitess calls authenticated users “actors”. Once VTAdmin has obtained an actor that they have not been granted access to via RBAC rules, that is a breach of security. An RBAC permission should only allow a user to carry out the actions against the resources that match the RBAC rules against the cluster or exploiting a vulnerability. Users can perform actions that they do not have permission to perform VTAdmins RBAC has two main goals: 1. Users should be able to perform the actions that

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 User and Permission Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTEGRITY_ERROR is returned on integrity error from MySQL, usually due to duplicate primary keys. PERMISSION_DENIED 6 PERMISSION_DENIED errors are returned when a user requests access to something that they don’t have reparent away from the current master to a replica tablet • upgrade old master tablet User and Permission Management Vitess uses its own mechanism for managing users and their permissions through VTGate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 User and Permission Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTEGRITY_ERROR is returned on integrity error from MySQL, usually due to duplicate primary keys. PERMISSION_DENIED 6 PERMISSION_DENIED errors are returned when a user requests access to something that they don’t have reparent away from the current master to a replica tablet • upgrade old master tablet User and Permission Management Vitess uses its own mechanism for managing users and their permissions. So the CREATE

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 User and Permission Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . reparent away from the current master to a replica tablet • upgrade old master tablet User and Permission Management Vitess uses its own mechanism for managing users and their permissions through VTGate

“RDS” flavor. This is because RDS did not support GTIDs when this was developed. With PlanetScale’s permission, this work will be leveraged to implement the new proposal. The work will be published as part

“RDS” flavor. This is because RDS did not support GTIDs when this was developed. With PlanetScale’s permission, this work will be leveraged to implement the new proposal. The work will be published as part

“RDS” flavor. This is because RDS did not support GTIDs when this was developed. With PlanetScale’s permission, this work will be leveraged to implement the new proposal. The work will be published as part

“RDS” flavor. This is because RDS did not support GTIDs when this was developed. With PlanetScale’s permission, this work will be leveraged to implement the new proposal. The work will be published as part