Phpmyadmin 4.5.5.1 dùng sql server phiên bản nào năm 2024

Since phpMyAdmin’s interface is based entirely in your browser, you’ll need a web server (such as Apache, nginx, ) to install phpMyAdmin’s files into.

PHP

• You need PHP 7.1.3 or newer, with session support, the Standard PHP Library (SPL) extension, hash, ctype, and JSON support.
• The mbstring extension (see ) is strongly recommended for performance reasons.
• To support uploading of ZIP files, you need the PHP zip extension.
• You need GD2 support in PHP to display inline thumbnails of JPEGs (“image/jpeg: inline”) with their original aspect ratio.
• When using the cookie authentication (the default), the openssl extension is strongly suggested.
• To support upload progress bars, see .
• To support XML and Open Document Spreadsheet importing, you need the libxml extension.
• To support reCAPTCHA on the login page, you need the openssl extension.
• To support displaying phpMyAdmin’s latest version, you need to enable`allow_url_open` in your php.ini or to have the curl extension.

Database

phpMyAdmin supports MySQL-compatible databases.

• MySQL 5.5 or newer
• MariaDB 5.5 or newer

Web browser

To access phpMyAdmin you need a web browser with cookies and JavaScript enabled.

You need a browser which is supported by jQuery 2.0, see .

phpMyAdmin is included in most Linux distributions. It is recommended to use distribution packages when possible - they usually provide integration to your distribution and you will automatically get security updates from your distribution.

Debian and Ubuntu

Most Debian and Ubuntu versions include a phpMyAdmin package, but be aware that the configuration file is maintained in

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

6 and may differ in some ways from the official phpMyAdmin documentation. Specifically, it does:

• Configuration of a web server (works for Apache and lighttpd).
• Creating of using dbconfig-common.
• Securing setup script, see .

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

See also

More information can be found in README.Debian (it is installed as

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

7 with the package).

Gentoo

Gentoo ships the phpMyAdmin package, both in a near-stock configuration as well as in a

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

8 configuration. Use

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

9 to install.

Mandriva

Mandriva ships the phpMyAdmin package in their

0 branch and can be installed via the usual Control Center.

Fedora

Fedora ships the phpMyAdmin package, but be aware that the configuration file is maintained in

1 and may differ in some ways from the official phpMyAdmin documentation.

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 . But be aware that the configuration file is maintained in

1 and may differ in some ways from the official phpMyAdmin documentation.

Installing on 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.

You can find more of such options at Wikipedia.

Installing from Git

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

• Git to download the source, or you can download the most recent source directly from Github
• Composer
• Node.js (version 10 or higher)
• Yarn

You can clone current phpMyAdmin source from

3:

git clone https://github.com/phpmyadmin/phpmyadmin.git

Additionally you need to install dependencies using Composer:

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

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

yarn install --production

Installing using Composer

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

Note

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=https://www.phpmyadmin.net/packages.json --no-dev

Installing using Docker

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

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

4 for phpMyAdmin (by specifying

5. 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).

Docker environment variables

You can configure several phpMyAdmin features using environment variables:

6

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

7

Hostname or IP address of the database server to use.

8

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

9

Verbose name of the database server.

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',
],

];

0

Comma-separated verbose name of the database servers.

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',
],

];

1

User name to use for .

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',
],

];

2

Password to use for .

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',
],

];

3

Port of the database server to use.

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',
],

];

4

Comma-separated ports of the database server to use.

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',
],

];

5

The fully-qualified path (

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',
],

];

6. where the reverse proxy makes phpMyAdmin available.

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',
],

];

7

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

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',
],

];

8

If set, this option will override the default value for apache and php-fpm (this will change

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',
],

];

9 and

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

0 values).

Note

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

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

1

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

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

2

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

By default, is used, but if and are set, it is switched to .

Note

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

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

5 when starting the MySQL container). Please check documentation for MariaDB container or MySQL container.

Customizing configuration

Additionally configuration can be tweaked by

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

6. 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/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php parameters.

Note that the supplied configuration file is applied after , 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:

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

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',
],

];

See also

See for detailed description of configuration options.

Docker Volumes

You can use the following volumes to customize image behavior:

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

6

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

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

8

Directory where PHP sessions are stored. You might want to share this for example when using .

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

9

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

Docker Examples

To connect phpMyAdmin to a given server use:

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

To connect phpMyAdmin to more servers use:

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

To use arbitrary server option:

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

You can also link the database container using Docker:

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

Running with additional configuration:

yarn install --production

0

Running with additional themes:

yarn install --production

1

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.

Customizing configuration file using docker-compose

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

yarn install --production

2

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:

yarn install --production

3

When using traefik, something like following should work:

yarn install --production

4

You then should specify in the docker-compose configuration:

yarn install --production

5

IBM Cloud

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

Quick Install

1. Choose an appropriate distribution kit from the phpmyadmin.net Downloads page. Some kits contain only the English messages, others contain all languages. We’ll assume you chose a kit whose name looks like docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 1.
2. Ensure you have downloaded a genuine archive, see .
3. Untar or unzip the distribution (be sure to unzip the subdirectories): docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 2 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. Ensure that all the scripts have the appropriate owner (if PHP is running in safe mode, having some scripts with an owner different from the owner of other scripts will be a problem). See and for suggestions.
5. Now you must configure your installation. There are two methods that can be used. Traditionally, users have hand-edited a copy of docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 3, but now a wizard-style setup script is provided for those who prefer a graphical installation. Creating a docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 3 is still a quick way to get started and needed for some advanced features.

Manually creating the file

To manually create the file, simply use your text editor to create the file

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

3 (you can copy

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

6 to get a minimal configuration file) in the main (top-level) phpMyAdmin directory (the one that contains

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

7). phpMyAdmin first loads

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

8 and then overrides those values with anything found in

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

3. If the default value is okay for a particular setting, there is no need to include it in

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

3. You’ll probably need only a few directives to get going; a simple configuration may look like this:

yarn install --production

6

Or, if you prefer to not be prompted every time you log in:

yarn install --production

7

Warning

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

For a full explanation of possible configuration values, see the of this document.

Using the Setup script

Instead of manually editing

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

3, 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

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

2 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. If you are using the docker run --name myadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin/phpmyadmin 3 “config”, it is suggested that you protect the phpMyAdmin installation directory because using config does not require a user to enter a password to access the phpMyAdmin installation. Use of an alternate authentication method is recommended, for example with HTTP–AUTH in a file or switch to using docker run --name myadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin/phpmyadmin 3 cookie or http. See the for additional information, especially .
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 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:

Verifying phpMyAdmin releases

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:

yarn install --production

8

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:

yarn install --production

9

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:

composer create-project phpmyadmin/phpmyadmin

0

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

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

5 files which contain the PGP signature for it. Once you have both of them in the same folder, you can verify the signature:

composer create-project phpmyadmin/phpmyadmin

1

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:

• Download the keyring from our download server, then import it with:

composer create-project phpmyadmin/phpmyadmin

2

• Download and import the key from one of the key servers:

composer create-project phpmyadmin/phpmyadmin

3

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:

composer create-project phpmyadmin/phpmyadmin

4

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 . 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.

Once the key is trusted, the warning will not occur:

composer create-project phpmyadmin/phpmyadmin

5

Should the signature be invalid (the archive has been changed), you would get a clear error regardless of the fact that the key is trusted or not:

composer create-project phpmyadmin/phpmyadmin

6

phpMyAdmin configuration storage

Changed in version 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 (, comments, -history, tracking mechanism, -generation, , 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).

Zero configuration

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 to false.

The following three scenarios are covered by the Zero Configuration mode:

• When entering a database where the configuration storage tables are not present, phpMyAdmin offers to create them from the Operations tab.
• When entering a database where the tables do already exist, the software automatically detects this and begins using them. This is the most common situation; after the tables are initially created automatically they are continually used without disturbing the user; this is also most useful on shared hosting where the user is not able to edit docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 3 and usually the user only has access to one database.
• When having access to multiple databases, if the user first enters the database containing the configuration storage tables then switches to another database, phpMyAdmin continues to use the tables from the first database; the user is not prompted to create more tables in the new database.

Manual configuration

Please look at your

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

8 directory, where you should find a file called create_tables.sql. (If you are using a Windows server, pay special attention to ).

If you already had this infrastructure and:

• upgraded to MySQL 4.1.2 or newer, please use docker run --name myadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin/phpmyadmin 9.
• upgraded to phpMyAdmin 4.3.0 or newer from 2.5.0 or newer (<= 4.2.x), please use docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin/phpmyadmin 0.
• upgraded to phpMyAdmin 4.7.0 or newer from 4.3.0 or newer, please use docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin/phpmyadmin 1.

and then create new tables by importing

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

2.

You can use your phpMyAdmin to create the tables for you. Please be aware that you may need special (administrator) privileges to create the database and tables, and that the script may need some tuning, depending on the database name.

After having imported the

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

2 file, you should specify the table names in your

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

3 file. The directives used for that can be found in the .

You will also need to have a controluser ( and settings) with the proper rights to those tables. For example you can create it using following statement:

And for any MariaDB version:

composer create-project phpmyadmin/phpmyadmin

7

For MySQL 8.0 and newer:

composer create-project phpmyadmin/phpmyadmin

8

For MySQL older than 8.0:

composer create-project phpmyadmin/phpmyadmin

9

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 for details.

Upgrading from an older version

Warning

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.

Simply copy

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

3 from your previous installation into the newly unpacked one. Configuration files from old versions may require some tweaking as some options have been changed or removed. For compatibility with PHP 5.3 and later, remove a

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

8 statement that you might find near the end of your configuration file.

You should not copy

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

8 over

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

3 because the default configuration file is version- specific.

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 yarn install --production 01).
3. Unpack freshly downloaded phpMyAdmin to the desired location (for example yarn install --production 02).
4. Copy yarn install --production 03 from old location ( yarn install --production
5. to the new one ( yarn install --production 02).
6. Test that everything works properly.
7. Remove backup of a previous version ( yarn install --production 01).

If you have upgraded your MySQL server from a version previous to 4.1.2 to version 5.x or newer and if you use the phpMyAdmin configuration storage, you should run the script found in

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

9.

If you have upgraded your phpMyAdmin to 4.3.0 or newer from 2.5.0 or newer (<= 4.2.x) and if you use the phpMyAdmin configuration storage, you should run the script found in

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

0.

Do not forget to clear the browser cache and to empty the old session by logging out and logging in again.

Using authentication modes

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 or cookie mode so that your user/password pair are not in clear in the configuration file.

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). 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:

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

0

What the user may now do is controlled entirely by the MySQL user management system. With HTTP or cookie authentication mode, you don’t need to fill the user/password fields inside the .

Cookie authentication mode

• Username and password are stored in cookies during the session and password is deleted when it ends.
• With this mode, the user can truly log out of phpMyAdmin and log back in with the same username (this is not possible with ).
• If you want to allow users to enter any hostname to connect (rather than only servers that are configured in docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 3), see the directive.
• As mentioned in the section, having the yarn install --production 13 extension will speed up access considerably, but is not required.

Signon authentication mode

• This mode is a convenient way of using credentials from another application to authenticate to phpMyAdmin to implement a single signon solution.
• The other application has to store login information into session data (see and) or you need to implement script to return the credentials (see).
• When no credentials are available, the user is being redirected to, where you should handle the login process.

The very basic example of saving credentials in a session is available as

yarn install --production

18:

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

1

Alternatively, you can also use this way to integrate with OpenID as shown in

yarn install --production

19:

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

2

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. There is a very minimal example in

yarn install --production

21:

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

3

Config authentication mode

• This mode is sometimes the less secure one because it requires you to fill the andfields (and as a result, anyone who can read your docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin 3 can discover your username and password).
• In the section, there is an entry explaining how to protect your configuration file.
• For additional security in this mode, you may wish to consider the Host authentication and configuration directives.
• Unlike cookie and http, does not require a user to log in when first loading the phpMyAdmin site. This is by design but could allow any user to access your installation. Use of some restriction method is suggested, perhaps a file with the HTTP-AUTH directive or disallowing incoming HTTP requests at one’s router or firewall will suffice (both of which are beyond the scope of this manual but easily searchable with Google).

Securing your phpMyAdmin installation

The phpMyAdmin team tries hard to make the application secure, however there are always ways to make your installation more secure:

• 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 should be disabled.
• Remove the yarn install --production 27 directory from phpMyAdmin, unless you are developing and need a test suite.
• Remove the yarn install --production 28 directory from phpMyAdmin, you will probably not use it after the initial setup.
• Properly choose an authentication method - is probably the best choice for shared hosting.
• Deny access to auxiliary files in yarn install --production 29 or yarn install --production 30 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 file in those directories.
• Deny access to temporary files, see (if that is placed inside your web root, see also .
• 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 yarn install --production 32 file in the root of your webserver or limit access by web server configuration, see .
• In case you don’t want all MySQL users to be able to access phpMyAdmin, you can use to limit them or to deny root user access.
• Enable for your account.
• Consider hiding phpMyAdmin behind an authentication proxy, so that users need to authenticate prior to providing MySQL credentials to phpMyAdmin. You can achieve this by configuring your web server to request HTTP authentication. For example in Apache this can be done with: composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev 4 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: composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev 5
• If you are afraid of automated attacks, enabling Captcha by and might be an option.
• Failed login attempts are logged to syslog (if available, see). 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 to achieve this.

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’

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

3, it can be impossible to log back in (when the logout comes manually or after a period of inactivity). Issue 11898.