phpMyAdmin no añade ninguna medida de seguridad al servidor de base de datos MySQL. El administrador de sistema es aún el responsable de otorgar adecuadamente los permisos sobre las bases de datos de MySQL. Se puede utilizar para ello la página de phpMyAdmin Usuarios.

Distribuciones de Linux

PhpMyAdmin esa incluído en la mayoria de las distribuciones Linux. Se recomienda que utilice los paquetes de la distribución cuando fuera posible - generalmente se integran con su distribución y recibirá automáticamente actualizaciones de seguridad desde su distribución.

Debian and Ubuntu

Most Debian and Ubuntu versions include a phpMyAdmin package, but be aware that the configuration file is maintained in /etc/phpmyadmin and may differ in some ways from the official phpMyAdmin documentation. Specifically, it does:

More specific details about installing Debian or Ubuntu packages are available in our wiki.

Ver también

More information can be found in README.Debian (it is installed as /usr/share/doc/phpmyadmin/README.Debian with the package).


OpenSUSE already comes with phpMyAdmin package, just install packages from the openSUSE Build Service.


Gentoo ships the phpMyAdmin package, both in a near-stock configuration as well as in a webapp-config configuration. Use emerge dev-db/phpmyadmin to install.


Mandriva provee el paquete de phpMyAdmin en su rama contrib y puede instalarlo de la forma usual con el Centro de control.


Fedora provee el paquete de phpMyAdmin, pero sepa que el archivo de configuración se encuentra en /etc/phpMyAdmin/ y puede tener diferencias con la documentación oficial de phpMyAdmin.

Red Hat Enterprise Linux

Red Hat Enterprise Linux itself and thus derivatives like CentOS don’t ship phpMyAdmin, but the Fedora-driven repository Extra Packages for Enterprise Linux (EPEL) is doing so, if it’s enabled. But be aware that the configuration file is maintained in /etc/phpMyAdmin/ and may differ in some ways from the official phpMyAdmin documentation.

Instalación en Windows

The easiest way to get phpMyAdmin on Windows is using third party products which include phpMyAdmin together with a database and web server such as XAMPP.

Puede encontrar más opciones similares en Wikipedia.

Instalación desde Git

In order to install from Git, you’ll need a few supporting applications:

You can clone current phpMyAdmin source from

git clone

Additionally you need to install dependencies using Composer:

composer update

If you do not intend to develop, you can skip the installation of developer tools by invoking:

composer update --no-dev

Finally, you’ll need to use Yarn to install some JavaScript dependencies:

yarn install --production

Instalación usando Composer

You can install phpMyAdmin using the Composer tool, since 4.7.0 the releases are automatically mirrored to the default Packagist repository.


The content of the Composer repository is automatically generated separately from the releases, so the content doesn’t have to be 100% same as when you download the tarball. There should be no functional differences though.

To install phpMyAdmin simply run:

composer create-project phpmyadmin/phpmyadmin

Alternatively you can use our own composer repository, which contains the release tarballs and is available at <>:

composer create-project phpmyadmin/phpmyadmin --repository-url= --no-dev

Instalación usando Docker

phpMyAdmin comes with a Docker official image, which you can easily deploy. You can download it using:

docker pull phpmyadmin

The phpMyAdmin server will listen on port 80. It supports several ways of configuring the link to the database server, either by Docker’s link feature by linking your database container to db for phpMyAdmin (by specifying --link your_db_host:db) or by environment variables (in this case it’s up to you to set up networking in Docker to allow the phpMyAdmin container to access the database container over the network).

Variables de entorno de Docker

Puede configurar varias características de phpMyAdmin usando variables de entorno:


Allows you to enter a database server hostname on login form.


Hostname or IP address of the database server to use.


Comma-separated hostnames or IP addresses of the database servers to use.


Usado únicamente si PMA_HOST está vacía.


Verbose name of the database server.


Comma-separated verbose name of the database servers.


Usado únicamente si PMA_VERBOSE está vacía.


Nombre de usuario a utilizar en Método de autenticación «config».


Contraseña a utilizar en Método de autenticación «config».


Port of the database server to use.


Comma-separated ports of the database server to use.


Used only if PMA_PORT is empty.


Socket file for the database connection.


Comma-separated list of socket files for the database connections.


Used only if PMA_SOCKET is empty.


The fully-qualified path ( where the reverse proxy makes phpMyAdmin available.

Ver también



When set to true, enables storing SQL history to $cfg['Servers'][$i]['pmadb']. When false, history is stored in the browser and is cleared when logging out.

Ver también



When set to an integer, controls the number of history items.


When set, this points to an alternate database host used for storing the «Almacenamiento de configuración de phpMyAdmin» database.


Defines the username for phpMyAdmin to use for the «Almacenamiento de configuración de phpMyAdmin» database.


Defines the password for phpMyAdmin to use for the «Almacenamiento de configuración de phpMyAdmin» database.


When set, will override the default port (3306) for connecting to the control host.


When set, define the name of the database to be used for the «Almacenamiento de configuración de phpMyAdmin» database. When not set, the advanced features are not enabled by default: they can still potentially be enabled by the user when logging in with the Sin configuración feature.


Suggested values: phpmyadmin or pmadb


If defined, this option will hide the PHP version (expose_php = Off). Set to any value (such as HIDE_PHP_VERSION=true).


If set, this option will override the default value for apache and php-fpm (this will change upload_max_filesize and post_max_size values).


Format as [0-9+](K,M,G) default value is 2048K


If set, this option will override the phpMyAdmin memory limit $cfg['MemoryLimit'] and PHP’s memory_limit.


Format as [0-9+](K,M,G) where K is for Kilobytes, M for Megabytes, G for Gigabytes and 1K = 1024 bytes. Default value is 512M.


If set, this option will override the maximum execution time in seconds for phpMyAdmin $cfg['ExecTimeLimit'] and PHP’s max_execution_time.


Format as [0-9+]. Default value is 600.


If set, this option will override the default with the base64 decoded contents of the variable.


If set, this option will override the default with the base64 decoded contents of the variable.


If set, this option will set the path where files can be saved to be available to import ($cfg['UploadDir'])


If set, this option will set the path where exported files can be saved ($cfg['SaveDir'])


If set, this option will change the default Apache port from 80 in case you want it to run on a different port like an unprivileged port. Set to any port value (such as APACHE_PORT=8090).

By default, Método de autenticación por cookie is used, but if PMA_USER and PMA_PASSWORD are set, it is switched to Método de autenticación «config».


The credentials you need to log in are stored in the MySQL server, in case of Docker image, there are various ways to set it (for example MYSQL_ROOT_PASSWORD when starting the MySQL container). Please check documentation for MariaDB container or MySQL container.

Personalizando configuración

Additionally configuration can be tweaked by /etc/phpmyadmin/ If this file exists, it will be loaded after configuration is generated from above environment variables, so you can override any configuration variable. This configuration can be added as a volume when invoking docker using -v /some/local/directory/ parameters.

Note that the supplied configuration file is applied after Variables de entorno de Docker, but you can override any of the values.

For example to change the default behavior of CSV export you can use the following configuration file:

$cfg['Export']['csv_columns'] = true;

You can also use it to define server configuration instead of using the environment variables listed in Variables de entorno de Docker:

/* Override Servers array */
$cfg['Servers'] = [
    1 => [
        'auth_type' => 'cookie',
        'host' => 'mydb1',
        'port' => 3306,
        'verbose' => 'Verbose name 1',
    2 => [
        'auth_type' => 'cookie',
        'host' => 'mydb2',
        'port' => 3306,
        'verbose' => 'Verbose name 2',

Ver también

See Configuración for detailed description of configuration options.

Docker Volumes

You can use the following volumes to customize image behavior:


Can be used for additional settings, see the previous chapter for more details.


Directory where PHP sessions are stored. You might want to share this for example when using Método de autenticación «signon».


Directory where phpMyAdmin looks for themes. By default only those shipped with phpMyAdmin are included, but you can include additional phpMyAdmin themes (see Custom Themes) by using Docker volumes.

Docker Examples

To connect phpMyAdmin to a given server use:

docker run --name phpmyadmin -d -e PMA_HOST=dbhost -p 8080:80 phpmyadmin:latest

To connect phpMyAdmin to more servers use:

docker run --name phpmyadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin:latest

To use arbitrary server option:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin:latest

You can also link the database container using Docker:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin:latest

Running with additional configuration:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/ phpmyadmin:latest

Running with additional themes:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/custom/phpmyadmin/themeName/:/var/www/html/themes/themeName/ phpmyadmin:latest

Using docker-compose

Alternatively, you can also use docker-compose with the docker-compose.yml from <>. This will run phpMyAdmin with an arbitrary server - allowing you to specify MySQL/MariaDB server on the login page.

docker compose up -d

Customizing configuration file using docker-compose

You can use an external file to customize phpMyAdmin configuration and pass it using the volumes directive:

    image: phpmyadmin:latest
    container_name: phpmyadmin
    restart: always
     - 8080:80
     - /sessions
     - ~/docker/phpmyadmin/
     - /custom/phpmyadmin/theme/:/www/themes/theme/

Running behind haproxy in a subdirectory

When you want to expose phpMyAdmin running in a Docker container in a subdirectory, you need to rewrite the request path in the server proxying the requests.

For example, using haproxy it can be done as:

frontend http
    bind *:80
    option forwardfor
    option http-server-close

    ### NETWORK restriction
    acl LOCALNET  src

    # /phpmyadmin
    acl phpmyadmin  path_dir /phpmyadmin
    use_backend phpmyadmin if phpmyadmin LOCALNET

backend phpmyadmin
    mode http

    reqirep  ^(GET|POST|HEAD)\ /phpmyadmin/(.*)     \1\ /\2

    # phpMyAdmin container IP
    server localhost

When using traefik, something like following should work:

defaultEntryPoints = ["http"]
  address = ":80"
      regex = "(http:\\/\\/[^\\/]+\\/([^\\?\\.]+)[^\\/])$"
      replacement = "$1/"


   backend = "myadmin"
   passHostHeader = true

You then should specify PMA_ABSOLUTE_URI in the docker-compose configuration:

version: '2'

    restart: always
    image: phpmyadmin:latest
    container_name: phpmyadmin
    hostname: phpmyadmin
      - 8000:80
      - PMA_HOSTS=,,,
      - PMA_VERBOSES=production-db1,production-db2,dev-db1,dev-db2
      - PMA_USER=root

IBM Cloud

One of our users has created a helpful guide for installing phpMyAdmin on the IBM Cloud platform.

Instalación rápida

  1. Choose an appropriate distribution kit from the Downloads page. Some kits contain only the English messages, others contain all languages. We’ll assume you chose a kit whose name looks like phpMyAdmin-x.x.x-all-languages.tar.gz.
  2. Asegúrese de que ha descargado un archivo genuino, vea Verificando lanzamientos de phpMyAdmin.
  3. Untar or unzip the distribution (be sure to unzip the subdirectories): tar -xzvf phpMyAdmin_x.x.x-all-languages.tar.gz in your webserver’s document root. If you don’t have direct access to your document root, put the files in a directory on your local machine, and, after step 4, transfer the directory on your web server using, for example, FTP.
  4. Asegúrese que todos los scripts tengan el dueño adecuado (si PHP está siendo ejecutado en modo seguro, tener algunos scripts con un dueño distinto al del de los demás scripts puede ser un problema. Revise 4.2 ¿Cuál es la forma preferida para asegurar phpMyAdmin contra accesos maliciosos? y 1.26 Acabo de instalar phpMyAdmin en la raíz de documentos de IIS pero obtengo el error «No se especificó archivo de entrada» al tratar de ejecutar phpMyAdmin. por sugerencias.
  5. Ahora debe configurar su instalación. Hay dos formas. Tradicionalmente, debía modificar a mano el archivo, pero ahora se suministra un archivo de configuración automático para aquellos que prefieran la instalación gráfica. Crear sigue siendo una manera rápida de empezar y es necesaria para algunas opciones avanzadas.

Creando el archivo en forma manual

To manually create the file, simply use your text editor to create the file (you can copy to get a minimal configuration file) in the main (top-level) phpMyAdmin directory (the one that contains index.php). phpMyAdmin first loads the default configuration values and then overrides those values with anything found in If the default value is okay for a particular setting, there is no need to include it in You’ll probably need only a few directives to get going; a simple configuration may look like this:

// The string is a hexadecimal representation of a 32-bytes long string of random bytes.
$cfg['blowfish_secret'] = sodium_hex2bin('f16ce59f45714194371b48fe362072dc3b019da7861558cd4ad29e4d6fb13851');

$cfg['Servers'][$i]['auth_type']     = 'cookie';
// if you insist on "root" having no password:
// $cfg['Servers'][$i]['AllowNoPassword'] = true;

O si prefiere no ser preguntado cada vez que quiera entrar:


$cfg['Servers'][$i]['user']          = 'root';
$cfg['Servers'][$i]['password']      = 'changeme'; // use here your password
$cfg['Servers'][$i]['auth_type']     = 'config';


Storing passwords in the configuration is insecure as anybody can then manipulate your database.

Si necesita conocer todos los valores de configuración disponibles, revise Configuración en este documento.

Using the Setup script

Instead of manually editing, you can use phpMyAdmin’s setup feature. The file can be generated using the setup and you can download it for upload to the server.

Next, open your browser and visit the location where you installed phpMyAdmin, with the /setup suffix. The changes are not saved to the server, you need to use the Download button to save them to your computer and then upload to the server.

Now the file is ready to be used. You can choose to review or edit the file with your favorite editor, if you prefer to set some advanced options that the setup script does not provide.

  1. Si está utilizando el método de autenticación «config» es preferible que proteja el directorio de instalación de phpMyAdmin porque el uso de este método no requiere que el usuario escriba su contraseña para acceder a la instalación de phpMyAdmin. Se recomienda el uso de métodos de autenticación alternativos, como por ejemplo un HTTP—AUTH en un archivo .htaccess o bien usar una autenticación http o por cookie. Revise ISPs, instalaciones multiusuario para obtener información adicional, especialmente 4.4 phpMyAdmin siempre devuelve «Acceso denegado» al utilizar autenticación HTTP..
  2. Open the main phpMyAdmin directory in your browser. phpMyAdmin should now display a welcome screen and your databases, or a login dialog if using HTTP or cookie authentication mode.

Setup script on Debian, Ubuntu and derivatives

Debian and Ubuntu have changed the way in which the setup script is enabled and disabled, in a way that single command has to be executed for either of these.

To allow editing configuration invoke:


To block editing configuration invoke:


Setup script on openSUSE

Some openSUSE releases do not include setup script in the package. In case you want to generate configuration on these you can either download original package from <> or use setup script on our demo server: <>.

Verificando lanzamientos de phpMyAdmin

Since July 2015 all phpMyAdmin releases are cryptographically signed by the releasing developer, who through January 2016 was Marc Delisle. His key id is 0xFEFC65D181AF644A, his PGP fingerprint is:

436F F188 4B1A 0C3F DCBF 0D79 FEFC 65D1 81AF 644A

and you can get more identification information from <>.

Beginning in January 2016, the release manager is Isaac Bennetch. His key id is 0xCE752F178259BD92, and his PGP fingerprint is:

3D06 A59E CE73 0EB7 1B51 1C17 CE75 2F17 8259 BD92

and you can get more identification information from <>.

Some additional downloads (for example themes) might be signed by Michal Čihař. His key id is 0x9C27B31342B7511D, and his PGP fingerprint is:

63CB 1DF1 EF12 CF2A C0EE 5A32 9C27 B313 42B7 511D

and you can get more identification information from <>.

You should verify that the signature matches the archive you have downloaded. This way you can be sure that you are using the same code that was released. You should also verify the date of the signature to make sure that you downloaded the latest version.

Each archive is accompanied by .asc files which contain the PGP signature for it. Once you have both of them in the same folder, you can verify the signature:

$ gpg --verify
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Can't check signature: public key not found

As you can see gpg complains that it does not know the public key. At this point, you should do one of the following steps:

$ gpg --import phpmyadmin.keyring
  • Descargue e importe la clave desde uno de los servidores de claves:
$ gpg --keyserver hkp:// --recv-keys 3D06A59ECE730EB71B511C17CE752F178259BD92
gpg: requesting key 8259BD92 from hkp server
gpg: key 8259BD92: public key "Isaac Bennetch <>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

This will improve the situation a bit - at this point, you can verify that the signature from the given key is correct but you still can not trust the name used in the key:

$ gpg --verify
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Good signature from "Isaac Bennetch <>"
gpg:                 aka "Isaac Bennetch <>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 3D06 A59E CE73 0EB7 1B51  1C17 CE75 2F17 8259 BD92

The problem here is that anybody could issue the key with this name. You need to ensure that the key is actually owned by the mentioned person. The GNU Privacy Handbook covers this topic in the chapter Validating other keys on your public keyring. The most reliable method is to meet the developer in person and exchange key fingerprints, however, you can also rely on the web of trust. This way you can trust the key transitively though signatures of others, who have met the developer in person.

Una vez se haya confiado en la clave, la advertencia no volverá a producirse:

$ gpg --verify
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Good signature from "Isaac Bennetch <>" [full]

La firma puede no ser válida (el fichero ha cambiado), debería obteer un error claro acerca del hecho de que la clave es confiable o no:

$ gpg --verify
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: BAD signature from "Isaac Bennetch <>" [unknown]

Almacenamiento de configuración de phpMyAdmin

Distinto en la versión 3.4.0: Prior to phpMyAdmin 3.4.0 this was called Linked Tables Infrastructure, but the name was changed due to the extended scope of the storage.

For a whole set of additional features (Favoritos, comments, SQL-history, tracking mechanism, PDF-generation, Transformaciones, Relaciones etc.) you need to create a set of special tables. Those tables can be located in your own database, or in a central database for a multi-user installation (this database would then be accessed by the controluser, so no other user should have rights to it).

Sin configuración

In many cases, this database structure can be automatically created and configured. This is called “Zero Configuration” mode and can be particularly useful in shared hosting situations. “ZeroConf” mode is on by default, to disable set $cfg['ZeroConf'] to false.

Los siguientes tres escenarios se cubren con el modo «Sin configuración»:

  • Cuando se accede a una base de datos donde las tablas de configuración de almacenamiento no están presentes, phpMyAdmin permite crearlas desde la pestaña de Operaciones.
  • Cuando se accede a una base de datos donde ya existen las tablas, el sofware las detecta automáticamente y las utiliza. Esta es la situación más común; Después de que las tablas se hayan creado inicialmente de modo automático, se usan continuamente sin molestar al usuario; Esto es muy util en hosting compartido, donde el usuario no puede editar el y solamente tiene acceso a una base de datos.
  • Cuando se tiene acceso a múltiples bases de datos, si el usuario accede primero a la base de datos que contiene las tablas de configuración de almacenamiento, y luego cambia a otra base de datos, phpMyAdmin continúa usando las tablas de la primera base de datos; No se le solicita al usuario que cree más tablas en la nueva base de datos.

Configuración manual

Por favor, mire su directorio «./sql/», donde debería encontrar un archivo llamado create_tables.sql. (Si está utilizando un servidor Windows preste especial atención a 1.23 Estoy ejecutando MySQL en un equipo de 32 bits con Windows. Cada vez que creo una nueva tabla ¡tanto la tabla como sus columnas cambian a minúsculas!).

Si ya tenía esta infraestructura y:

  • actualizado a MySQL 4.1.2 o posterior, utilice sql/upgrade_tables_mysql_4_1_2+.sql.
  • actualizado a phpMyAdmin 4.3.0 o posterior desde 2.5.0 o posterior (<= 4.2.x), utilice sql/upgrade_column_info_4_3_0+.sql.
  • upgraded to phpMyAdmin 4.7.0 or newer from 4.3.0 or newer, please use sql/upgrade_tables_4_7_0+.sql.

y luego cree las nuevas tablas importando sql/create_tables.sql.

Puede hacer que phpMyAdmin cree automáticamente las tablas. Tenga en cuenta que se necesitan privilegios especiales (de administrador) para crear la base de datos y las tablas, y que el script puede necesitar algunas modificaciones dependiendo del nombre de la base de datos.

Tras haber importado el archivo sql/create_tables.sql, debería especificar los nombres de las tablas en su archivo Las directivas necesarias están disponibles en Configuración.

También necesitará un usuario de control (las configuraciones $cfg['Servers'][$i]['controluser'] y $cfg['Servers'][$i]['controlpass']) con los permisos apropiados para esas tablas. Puede crearlos, por ejemplo, utilizando la siguiente sentencia:

And for any MariaDB version:

CREATE USER 'pma'@'localhost' IDENTIFIED VIA mysql_native_password USING 'pmapass';
GRANT SELECT, INSERT, UPDATE, DELETE ON `<pma_db>`.* TO 'pma'@'localhost';

For MySQL 8.0 and newer:

CREATE USER 'pma'@'localhost' IDENTIFIED WITH caching_sha2_password BY 'pmapass';
GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';

For MySQL older than 8.0:

CREATE USER 'pma'@'localhost' IDENTIFIED WITH mysql_native_password AS 'pmapass';
GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';

Note that MySQL installations with PHP older than 7.4 and MySQL newer than 8.0 may require using the mysql_native_password authentication as a workaround, see 1.45 I get an error message about unknown authentication method caching_sha2_password when trying to log in for details.

Actualizando desde una versión más antigua


Never extract the new version over an existing installation of phpMyAdmin, always first remove the old files keeping just the configuration.

This way, you will not leave any old or outdated files in the directory, which can have severe security implications or can cause various breakages.

Simplemente copie el archivo de su antigua instalación en la recién descomprimida. Los archivos de configuración de versiones previas pueden requerir algunas modificaciones dado que algunas opciones pueden haber sido cambiadas o eliminadas. Por compatibilidad con PHP 5.3 o posterior, elimine la sentencia set_magic_quotes_runtime(0); que pueda encontrar cerca del final de su archivo de configuración.

The complete upgrade can be performed in a few simple steps:

  1. Download the latest phpMyAdmin version from <>.
  2. Rename existing phpMyAdmin folder (for example to phpmyadmin-old).
  3. Unpack freshly downloaded phpMyAdmin to the desired location (for example phpmyadmin).
  4. Copy` from old location (phpmyadmin-old) to the new one (phpmyadmin).
  5. Test that everything works properly.
  6. Remove backup of a previous version (phpmyadmin-old).

Si ha actualizado su servidor MySQL desde una versión anterior a la 4.1.2 a una versión 5.x o más reciente y está utilizando el almacenamiento de configuración phpMyAdmin, debería ejecutar el script SQL que se encuentra en sql/upgrade_tables_mysql_4_1_2+.sql.

Si ha actualizado su phpMyAdmin a la versión 4.3.0 o posterior desde una 2.5.0 o posterior (<= 4.2.x) y utiliza el almacenamiento de configuración de phpMyAdmin, debería ejecutar el script SQL que se encuentra en sql/upgrade_column_info_4_3_0+.sql.

No olvide limpiar la caché del navegador y vaciar la sesión antigua realizando logout y volviendo a identificarse de nuevo.

Uso de los métodos de autenticación

HTTP and cookie authentication modes are recommended in a multi-user environment where you want to give users access to their own database and don’t want them to play around with others. Nevertheless, be aware that MS Internet Explorer seems to be really buggy about cookies, at least till version 6. Even in a single-user environment, you might prefer to use HTTP or cookie mode so that your user/password pair are not in clear in the configuration file.

HTTP and cookie authentication modes are more secure: the MySQL login information does not need to be set in the phpMyAdmin configuration file (except possibly for the $cfg['Servers'][$i]['controluser']). However, keep in mind that the password travels in plain text unless you are using the HTTPS protocol. In cookie mode, the password is stored, encrypted with the AES algorithm, in a temporary cookie.

Then each of the true users should be granted a set of privileges on a set of particular databases. Normally you shouldn’t give global privileges to an ordinary user unless you understand the impact of those privileges (for example, you are creating a superuser). For example, to grant the user real_user with all privileges on the database user_base:

GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';

Lo que el usuario pueda hacer a continuación es controlado exclusivamente por el sistema de administración de usuarios de MySQL. Con los métodos de autenticación HTTP o por cookie, no es necesario rellenar los campos usuario/contraseña en $cfg['Servers'].

Modo de autenticación HTTP


There is no way to do proper logout in HTTP authentication, most browsers will remember credentials until there is no different successful authentication. Because of this, this method has a limitation that you can not login with the same user after logout.

Método de autenticación «signon»

Puede encontrar un ejemplo básico para guardar las credenciales en una sesión en examples/signon.php:

 * Single signon for phpMyAdmin
 * This is just example how to use session based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.


/* Use cookies for session */
ini_set('session.use_cookies', 'true');
/* Change this to true if using phpMyAdmin over https */
$secureCookie = false;
/* Need to have cookie visible from parent directory */
session_set_cookie_params(0, '/', '', $secureCookie, true);
/* Create signon session */
$sessionName = 'SignonSession';
// Uncomment and change the following line to match your $cfg['SessionSavePath']

/* Was data posted? */
if (isset($_POST['user'])) {
    /* Store there credentials */
    $_SESSION['PMA_single_signon_user'] = $_POST['user'];
    $_SESSION['PMA_single_signon_password'] = $_POST['password'];
    $_SESSION['PMA_single_signon_host'] = $_POST['host'];
    $_SESSION['PMA_single_signon_port'] = $_POST['port'];
    /* Update another field of server configuration */
    $_SESSION['PMA_single_signon_cfgupdate'] = ['verbose' => 'Signon test'];
    $_SESSION['PMA_single_signon_HMAC_secret'] = hash('sha1', uniqid(strval(random_int(0, mt_getrandmax())), true));
    $id = session_id();
    /* Close that session */
    /* Redirect to phpMyAdmin (should use absolute URL here!) */
    header('Location: ../index.php');
} else {
    /* Show simple form */
    header('Content-Type: text/html; charset=utf-8');

    echo '<?xml version="1.0" encoding="utf-8"?>' . "\n";
    echo '<!DOCTYPE HTML>
<html lang="en" dir="ltr">
<link rel="icon" href="../favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="../favicon.ico" type="image/x-icon">
<meta charset="utf-8">
<title>phpMyAdmin single signon example</title>

    if (isset($_SESSION['PMA_single_signon_error_message'])) {
        echo '<p class="error">';
        echo $_SESSION['PMA_single_signon_error_message'];
        echo '</p>';

    echo '<form action="signon.php" method="post">
Username: <input type="text" name="user" autocomplete="username" spellcheck="false"><br>
Password: <input type="password" name="password" autocomplete="current-password" spellcheck="false"><br>
Host: (will use the one from by default)
<input type="text" name="host"><br>
Port: (will use the one from by default)
<input type="text" name="port"><br>
<input type="submit">

Alternatively, you can also use this way to integrate with OpenID as shown in examples/openid.php:

 * Single signon for phpMyAdmin using OpenID
 * This is just example how to use single signon with phpMyAdmin, it is
 * not intended to be perfect code and look, only shows how you can
 * integrate this functionality in your application.
 * It uses OpenID pear package, see
 * User first authenticates using OpenID and based on content of $AUTH_MAP
 * the login information is passed to phpMyAdmin in session data.


if (false === @include_once 'OpenID/RelyingParty.php') {

/* Change this to true if using phpMyAdmin over https */
$secureCookie = false;

 * Map of authenticated users to MySQL user/password pairs.
$authMap = ['' => ['user' => 'root', 'password' => '']];

// phpcs:disable PSR1.Files.SideEffects,Squiz.Functions.GlobalFunction

 * Simple function to show HTML page with given content.
 * @param string $contents Content to include in page
function Show_page(string $contents): void
    header('Content-Type: text/html; charset=utf-8');

    echo '<?xml version="1.0" encoding="utf-8"?>' . "\n";
    echo '<!DOCTYPE HTML>
<html lang="en" dir="ltr">
<link rel="icon" href="../favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="../favicon.ico" type="image/x-icon">
<meta charset="utf-8">
<title>phpMyAdmin OpenID signon example</title>

    if (isset($_SESSION['PMA_single_signon_error_message'])) {
        echo '<p class="error">' . $_SESSION['PMA_single_signon_message'] . '</p>';

    echo $contents;
    echo '</body></html>';

 * Display error and exit
 * @param Exception $e Exception object
function Die_error(Throwable $e): void
    $contents = "<div class='relyingparty_results'>\n";
    $contents .= '<pre>' . htmlspecialchars($e->getMessage()) . "</pre>\n";
    $contents .= "</div class='relyingparty_results'>";

// phpcs:enable

/* Need to have cookie visible from parent directory */
session_set_cookie_params(0, '/', '', $secureCookie, true);
/* Create signon session */
$sessionName = 'SignonSession';

// Determine realm and return_to
$base = 'http';
if (isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] === 'on') {
    $base .= 's';

$base .= '://' . $_SERVER['SERVER_NAME'] . ':' . $_SERVER['SERVER_PORT'];

$realm = $base . '/';
$returnTo = $base . dirname($_SERVER['PHP_SELF']);
if ($returnTo[strlen($returnTo) - 1] !== '/') {
    $returnTo .= '/';

$returnTo .= 'openid.php';

/* Display form */
if ((! count($_GET) && ! count($_POST)) || isset($_GET['phpMyAdmin'])) {
    /* Show simple form */
    $content = '<form action="openid.php" method="post">
OpenID: <input type="text" name="identifier"><br>
<input type="submit" name="start">

/* Grab identifier */
$identifier = null;
if (isset($_POST['identifier']) && is_string($_POST['identifier'])) {
    $identifier = $_POST['identifier'];
} elseif (isset($_SESSION['identifier']) && is_string($_SESSION['identifier'])) {
    $identifier = $_SESSION['identifier'];

/* Create OpenID object */
try {
    $o = new OpenID_RelyingParty($returnTo, $realm, $identifier);
} catch (Throwable $e) {

/* Redirect to OpenID provider */
if (isset($_POST['start'])) {
    try {
        $authRequest = $o->prepare();
    } catch (Throwable $e) {

    $url = $authRequest->getAuthorizeURL();

    header('Location: ' . $url);

/* Grab query string */
if (! count($_POST)) {
    [, $queryString] = explode('?', $_SERVER['REQUEST_URI']);
} else {
    // Fetch the raw query body
    $queryString = file_get_contents('php://input');

/* Check reply */
try {
    $message = new OpenID_Message($queryString, OpenID_Message::FORMAT_HTTP);
} catch (Throwable $e) {

$id = $message->get('openid.claimed_id');

if (empty($id) || ! isset($authMap[$id])) {
    Show_page('<p>User not allowed!</p>');

$_SESSION['PMA_single_signon_user'] = $authMap[$id]['user'];
$_SESSION['PMA_single_signon_password'] = $authMap[$id]['password'];
$_SESSION['PMA_single_signon_HMAC_secret'] = hash('sha1', uniqid(strval(random_int(0, mt_getrandmax())), true));
/* Redirect to phpMyAdmin (should use absolute URL here!) */
header('Location: ../index.php');

If you intend to pass the credentials using some other means than, you have to implement wrapper in PHP to get that data and set it to $cfg['Servers'][$i]['SignonScript']. There is a very minimal example in examples/signon-script.php:

 * Single signon for phpMyAdmin
 * This is just example how to use script based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.


// phpcs:disable Squiz.Functions.GlobalFunction

 * This function returns username and password.
 * It can optionally use configured username as parameter.
 * @param string $user User name
 * @return array<int,string>
function get_login_credentials(string $user): array
    /* Optionally we can use passed username */
    if (! empty($user)) {
        return [$user, 'password'];

    /* Here we would retrieve the credentials */
    return ['root', ''];

Método de autenticación «config»

  • Este método a veces es el más inseguro dado que necesita que se rellenen los campos $cfg['Servers'][$i]['user'] y $cfg['Servers'][$i]['password'] (y, por ello, cualquiera que pueda leer el archivo podrá leer su nombre de usuario y contraseña).
  • En la sección ISPs, instalaciones multiusuario, hay una reseña que explica cómo proteger su archivo de configuración.
  • Para incrementar la seguridad en este modo, debería considerar el uso de las directivas de autenticación del servidor $cfg['Servers'][$i]['AllowDeny']['order'] y $cfg['Servers'][$i]['AllowDeny']['rules'].
  • A diferencia de los métodos «cookie» y «HTTP», no pide al usuario que se autentique al cargar la página phpMyAdmin por primera vez. Esto es así por diseño pero podría permitir a cualquiera entrar en su instalación. Debería emplear un método de restricción, como un archivo .htaccess con la directiva HTTP-AUTH o impedir las consultas HTTP entrantes a su router o firewall (ambos métodos están más allá de la temática de este manual, pero son fácilmente localizables con Google).

Asegurando su instalación de phpMyAdmin

El equipo de phpMyAdmin trabaja muy duro intentando hacer segura la aplicación, sin embargo siempre puede hacer su instalación más segura:

  • Follow our Security announcements and upgrade phpMyAdmin whenever new vulnerability is published.

  • Serve phpMyAdmin on HTTPS only. Preferably, you should use HSTS as well, so that you’re protected from protocol downgrade attacks.

  • Ensure your PHP setup follows recommendations for production sites, for example display_errors should be disabled.

  • Remove the test directory from phpMyAdmin, unless you are developing and need a test suite.

  • Elimine el directorio setup de phpMyAdmin, probablemente no lo utilizará después de la configuración inicial.

  • Elija el método de autenticación apropiado - Método de autenticación por cookie es probablemente la mejor opción para servidores compartidos.

  • Deny access to auxiliary files in ./libraries/ or ./templates/ subfolders in your webserver configuration. Such configuration prevents from possible path exposure and cross side scripting vulnerabilities that might happen to be found in that code. For the Apache webserver, this is often accomplished with a .htaccess file in those directories.

  • Deny access to temporary files, see $cfg['TempDir'] (if that is placed inside your web root, see also Directorios en el servidor web para subir/guardar/importar.

  • It is generally a good idea to protect a public phpMyAdmin installation against access by robots as they usually can not do anything good there. You can do this using robots.txt file in the root of your webserver or limit access by web server configuration, see 1.42 ¿Cómo puedo evitar que robots accedan a phpMyAdmin?.

  • In case you don’t want all MySQL users to be able to access phpMyAdmin, you can use $cfg['Servers'][$i]['AllowDeny']['rules'] to limit them or $cfg['Servers'][$i]['AllowRoot'] to deny root user access.

  • Enable Autenticación de dos factores for your account.

  • Considere ocultar phpMyAdmin tras un proxy que requiera autenticación, de modo que los usuarios necesiten autenticarse antes de proporcionar las credenciales MySQL a phpMyAdmin. Puede conseguirlo configurando su servidor web para que solicite autenticación HTTP. Por ejemplo, en Apache puede realizarse con:

    AuthType Basic
    AuthName "Restricted Access"
    AuthUserFile /usr/share/phpmyadmin/passwd
    Require valid-user

    Once you have changed the configuration, you need to create a list of users which can authenticate. This can be done using the htpasswd utility:

    htpasswd -c /usr/share/phpmyadmin/passwd username
  • Si teme a ataques automáticos, activar Captcha con $cfg['CaptchaLoginPublicKey'] y $cfg['CaptchaLoginPrivateKey'] puede ser una opción.

  • Failed login attempts are logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or access log files.

  • In case you’re running phpMyAdmin together with other PHP applications, it is generally advised to use separate session storage for phpMyAdmin to avoid possible session-based attacks against it. You can use $cfg['SessionSavePath'] to achieve this.

Using SSL for connection to database server

It is recommended to use SSL when connecting to remote database server. There are several configuration options involved in the SSL setup:

Defines whether to use SSL at all. If you enable only this, the connection will be encrypted, but there is not authentication of the connection - you can not verify that you are talking to the right server.
$cfg['Servers'][$i]['ssl_key'] and $cfg['Servers'][$i]['ssl_cert']
This is used for authentication of client to the server.
$cfg['Servers'][$i]['ssl_ca'] and $cfg['Servers'][$i]['ssl_ca_path']
The certificate authorities you trust for server certificates. This is used to ensure that you are talking to a trusted server.
This configuration disables server certificate verification. Use with caution.

When the database server is using a local connection or private network and SSL can not be configured you can use $cfg['MysqlSslWarningSafeHosts'] to explicitly list the hostnames that are considered secure.

Known issues

Users with column-specific privileges are unable to «Browse»

If a user has only column-specific privileges on some (but not all) columns in a table, «Browse» will fail with an error message.

As a workaround, a bookmarked query with the same name as the table can be created, this will run when using the «Browse» link instead. Issue 11922.

Trouble logging back in after logging out using “http” authentication

When using the “http” auth_type, it can be impossible to log back in (when the logout comes manually or after a period of inactivity). Issue 11898.