. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 vtctl Schema, Version, Permissions Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . which are assumed to provide a distributed, consistent key-value store. The default topology service plugin is etcd2. The topology service exists for several reasons: 14 • It enables tablets to coordinate Documentation • Execution Plans vtworker vtworker hosts long-running processes. It supports a plugin architecture and offers libraries so that you can easily choose tablets to use. Plugins are available

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Older Version Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 vtctl Schema, Version, Permissions Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Older Version Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 vtctl Schema, Version, Permissions Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Older Version Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 vtctl Schema, Version, Permissions Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 description: User guides for features in older version of Vitess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Horizontal Sharding

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Older Version Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 vtctl Schema, Version, Permissions Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Basic Flow for version tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Older Version Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 vtctl Schema, Version, Permissions Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Schema, Version, Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . which are assumed to provide a distributed, consistent key-value store. The default topology service plugin is etcd2. The topology service exists for several reasons: • It enables tablets to coordinate among their underlying MySQL instances. vtworker vtworker hosts long-running processes. It supports a plugin architecture and offers libraries so that you can easily choose tablets to use. Plugins are available

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Schema, Version, Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . which are assumed to provide a distributed, consistent key-value store. The default topology service plugin is etcd2. The topology service exists for several reasons: • It enables tablets to coordinate among their underlying MySQL instances. vtworker vtworker hosts long-running processes. It supports a plugin architecture and offers libraries so that you can easily choose tablets to use. Plugins are available

Vitess links to an example authentication plugin which is available here: https://gist.github.com/ajm188/5b2c7d3ca76004a297e6e279a54c2299. This example plugin extracts the actor from either the context from a cookie. 6 Vitess Security Audit, 2023 When a Vitess administrator adds an authentication plugin, VTAdmin-api adds it as a middleware at the http mux layer. VTAdmin-api does this in vitess/go/vt/vtadmin/api the routes are initialized: First VTAdmin-api checks if the user has registered an authentication plugin: And later, it gets added to the http mux layer: Authorization Once a request has been authenticated

operation on the server-side and compares the client's authentication token directly with its own version of the scrambled password, rendering the attack described below possible. In this scenario, if the