Запуск phpmyadmin на windows

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:

• Configuration of a web server (works for Apache and lighttpd).

• Creating of phpMyAdmin configuration storage using dbconfig-common.

• Securing setup script, see Setup script on Debian, Ubuntu and derivatives.

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

OpenSUSE

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

Gentoo

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

Mandriva ships the phpMyAdmin package in their contrib 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 /etc/phpMyAdmin/ 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
enabled.
But be aware that the configuration file is maintained in
/etc/phpMyAdmin/ and may differ in some ways from the
official phpMyAdmin documentation.

Docker environment variables

You can configure several phpMyAdmin features using environment variables:

PMA_ARBITRARY

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

PMA_HOST

Hostname or IP address of the database server to use.

PMA_HOSTS

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

Note

Used only if PMA_HOST is empty.

PMA_VERBOSE

Verbose name of the database server.

PMA_VERBOSES

Comma-separated verbose name of the database servers.

Note

Used only if PMA_VERBOSE is empty.

PMA_USER

User name to use for Config authentication mode.

PMA_PASSWORD

Password to use for Config authentication mode.

PMA_PORT

Port of the database server to use.

PMA_PORTS

Comma-separated ports of the database server to use.

Note

Used only if PMA_PORT is empty.

PMA_SOCKET

Socket file for the database connection.

PMA_SOCKETS

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

Note

Used only if PMA_SOCKET is empty.

PMA_ABSOLUTE_URI

The fully-qualified path (https://pma.example.net/) where the reverse
proxy makes phpMyAdmin available.

PMA_QUERYHISTORYDB

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.

PMA_QUERYHISTORYMAX

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

PMA_CONTROLHOST

When set, this points to an alternate database host used for storing the “phpMyAdmin configuration storage” database.

PMA_CONTROLUSER

Defines the username for phpMyAdmin to use for the “phpMyAdmin configuration storage” database.

PMA_CONTROLPASS

Defines the password for phpMyAdmin to use for the “phpMyAdmin configuration storage” database.

PMA_CONTROLPORT

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

PMA_PMADB

When set, define the name of the database to be used for the “phpMyAdmin configuration storage” 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 Zero configuration feature.

Note

Suggested values: phpmyadmin or pmadb

HIDE_PHP_VERSION

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

UPLOAD_LIMIT

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

Note

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

MEMORY_LIMIT

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

Note

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.

MAX_EXECUTION_TIME

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

Note

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

PMA_CONFIG_BASE64

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

PMA_USER_CONFIG_BASE64

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

PMA_UPLOADDIR

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

PMA_SAVEDIR

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

APACHE_PORT

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

PMA_SSL_DIR

Define the path used for SSL files generated from environment variables, default value is /etc/phpmyadmin/ssl.

PMA_SSL

When set to 1, defines SSL usage for the MySQL connection.

PMA_SSLS

Comma-separated list of 0 and 1 defining SSL usage for the corresponding MySQL connections.

PMA_SSL_VERIFY

When set to 1, enables SSL certificate verification for the MySQL connection.

PMA_SSL_VERIFIES

Comma-separated list of 0 and 1 to enable or disable SSL certificate verification for multiple MySQL connections.

PMA_SSL_CA

In the context of mutual TLS security, allows setting your CA file as a string inside the default config.inc.php.

PMA_SSL_CAS

In the context of mutual TLS security, allows setting multiple CA files as a comma-separated list of strings inside the default config.inc.php.

PMA_SSL_CA_BASE64

In the context of mutual TLS security, allows setting your CA file as a base64 string inside the default config.inc.php.

PMA_SSL_CAS_BASE64

In the context of mutual TLS security, allows setting multiple CA files as a comma-separated list of base64 strings inside the default config.inc.php.

PMA_SSL_CERT

In the context of mutual TLS security, allows setting your CERT file as a string inside the default config.inc.php.

PMA_SSL_CERTS

In the context of mutual TLS security, allows setting multiple CERT files as a comma-separated list of strings inside the default config.inc.php.

PMA_SSL_CERT_BASE64

In the context of mutual TLS security, allows setting your CERT file as a base64 string inside the default config.inc.php.

PMA_SSL_CERTS_BASE64

In the context of mutual TLS security, allows setting multiple CERT files as a comma-separated list of base64 strings inside the default config.inc.php.

PMA_SSL_KEY

In the context of mutual TLS security, allows setting your KEY file as a string inside the default config.inc.php.

PMA_SSL_KEYS

In the context of mutual TLS security, allows setting multiple KEY files as a comma-separated list of strings inside the default config.inc.php.

PMA_SSL_KEY_BASE64

In the context of mutual TLS security, allows setting your KEY file as a base64 string inside the default config.inc.php.

PMA_SSL_KEYS_BASE64

In the context of mutual TLS security, allows setting multiple KEY files as a comma-separated list of base64 strings inside the default config.inc.php.

TZ

If defined, this option will change the default PHP date.timezone from UTC.

By default, Cookie authentication mode is used, but if PMA_USER and
PMA_PASSWORD are set, it is switched to Config authentication mode.

Customizing configuration

Additionally configuration can be tweaked by /etc/phpmyadmin/config.user.inc.php. 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 Docker environment variables,
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:

<?php
$cfg['Export']['csv_columns'] = true;

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

<?php
/* 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',
    ],
];

Docker Volumes

You can use the following volumes to customize image behavior:

/etc/phpmyadmin/config.user.inc.php

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

/sessions/

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

/www/themes/

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/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php 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
<https://github.com/phpmyadmin/docker>. 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:

phpmyadmin:
    image: phpmyadmin:latest
    container_name: phpmyadmin
    environment:
     - PMA_ARBITRARY=1
    restart: always
    ports:
     - 8080:80
    volumes:
     - /sessions
     - ~/docker/phpmyadmin/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php
     - /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 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12

    # /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     172.30.21.21:80

When using traefik, something like following should work:

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

[backends]
  [backends.myadmin]
    [backends.myadmin.servers.myadmin]
    url="http://internal.address.to.pma"

[frontends]
   [frontends.myadmin]
   backend = "myadmin"
   passHostHeader = true
     [frontends.myadmin.routes.default]
     rule="PathPrefixStrip:/phpmyadmin/;AddPrefix:/"

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

version: '2'

services:
  phpmyadmin:
    restart: always
    image: phpmyadmin:latest
    container_name: phpmyadmin
    hostname: phpmyadmin
    domainname: example.com
    ports:
      - 8000:80
    environment:
      - PMA_HOSTS=172.26.36.7,172.26.36.8,172.26.36.9,172.26.36.10
      - PMA_VERBOSES=production-db1,production-db2,dev-db1,dev-db2
      - PMA_USER=root
      - PMA_PASSWORD=
      - PMA_ABSOLUTE_URI=http://example.com/phpmyadmin/

Manually creating the file

To manually create the file, simply use your text editor to create the
file config.inc.php (you can copy config.sample.inc.php 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 config.inc.php. If the default value is
okay for a particular setting, there is no need to include it in
config.inc.php. You’ll probably need only a few directives to get going; a
simple configuration may look like this:

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

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

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

<?php

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

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

Using the Setup script

Instead of manually editing config.inc.php, 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. If you are using the auth_type “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 .htaccess file or switch to using
   auth_type cookie or http. See the ISPs, multi-user installations
   for additional information, especially 4.4 phpMyAdmin always gives “Access denied” when using HTTP authentication..

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.

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 $cfg['ZeroConf'] 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 config.inc.php 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 ./sql/ directory, where you should find a
file called create_tables.sql. (If you are using a Windows server,
pay special attention to 1.23 I’m running MySQL on a Win32 machine. Each time I create a new table the table and column names are changed to lowercase!).

If you already had this infrastructure and:

• upgraded to MySQL 4.1.2 or newer, please use
  sql/upgrade_tables_mysql_4_1_2+.sql.

• upgraded to phpMyAdmin 4.3.0 or newer from 2.5.0 or newer (<= 4.2.x),
  please use 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.

and then create new tables by importing sql/create_tables.sql.

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 sql/create_tables.sql file, you
should specify the table names in your config.inc.php file. The
directives used for that can be found in the Configuration.

You will also need to have a controluser
($cfg['Servers'][$i]['controluser'] and
$cfg['Servers'][$i]['controlpass'] settings)
with the proper rights to those tables. For example you can create it
using following statement:

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.

HTTP authentication mode

• Uses HTTP Basic authentication
  method and allows you to log in as any valid MySQL user.

• Is supported with most PHP configurations. For IIS (ISAPI)
  support using CGI PHP see 1.32 Can I use HTTP authentication with IIS?, for using with Apache
  CGI see 1.35 Can I use HTTP authentication with Apache CGI?.

• When PHP is running under Apache’s mod_proxy_fcgi (e.g. with PHP-FPM),
  Authorization headers are not passed to the underlying FCGI application,
  such that your credentials will not reach the application. In this case, you can
  add the following configuration directive:

  SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
  

• See also 4.4 phpMyAdmin always gives “Access denied” when using HTTP authentication. about not using the .htaccess mechanism along with
  ‘HTTP’ authentication mode.

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 HTTP authentication mode).

• If you want to allow users to enter any hostname to connect (rather than only
  servers that are configured in config.inc.php),
  see the $cfg['AllowArbitraryServer'] directive.

• As mentioned in the Requirements section, having the openssl 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 $cfg['Servers'][$i]['SignonSession'] and
  $cfg['Servers'][$i]['SignonCookieParams']) or you
  need to implement script to return the credentials (see
  $cfg['Servers'][$i]['SignonScript']).

• When no credentials are available, the user is being redirected to
  $cfg['Servers'][$i]['SignonURL'], where you should handle
  the login process.

The very basic example of saving credentials in a session is available as
examples/signon.php:

<?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.
 */

declare(strict_types=1);

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

/* 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 */
    @session_write_close();
    /* 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">
<head>
<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>
</head>
<body>';

    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 config.inc.php by default)
<input type="text" name="host"><br>
Port: (will use the one from config.inc.php by default)
<input type="text" name="port"><br>
<input type="submit">
</form>
</body>
</html>';
}

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

<?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 https://pear.php.net/package/OpenID
 *
 * User first authenticates using OpenID and based on content of $AUTH_MAP
 * the login information is passed to phpMyAdmin in session data.
 */

declare(strict_types=1);

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

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

/**
 * Map of authenticated users to MySQL user/password pairs.
 */
$AUTH_MAP = [
    'https://launchpad.net/~username' => [
        '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($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">
<head>
<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>
</head>
<body>';

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

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

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

// phpcs:enable

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

// 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">
</form>';
    Show_page($content);
    exit;
}

/* 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) {
    Die_error($e);
}

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

    $url = $authRequest->getAuthorizeURL();

    header('Location: ' . $url);
    exit;
}

/* 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) {
    Die_error($e);
}

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

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

$_SESSION['PMA_single_signon_user'] = $AUTH_MAP[$id]['user'];
$_SESSION['PMA_single_signon_password'] = $AUTH_MAP[$id]['password'];
$_SESSION['PMA_single_signon_HMAC_secret'] = hash('sha1', uniqid(strval(random_int(0, mt_getrandmax())), true));
session_write_close();
/* 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:

<?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.
 */

declare(strict_types=1);

// 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
 */
function get_login_credentials($user)
{
    /* Optionally we can use passed username */
    if (! empty($user)) {
        return [
            $user,
            'password',
        ];
    }

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

Config authentication mode

• This mode is sometimes the less secure one because it requires you to fill the
  $cfg['Servers'][$i]['user'] and
  $cfg['Servers'][$i]['password']
  fields (and as a result, anyone who can read your config.inc.php
  can discover your username and password).

• In the ISPs, multi-user installations 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 $cfg['Servers'][$i]['AllowDeny']['order']
  and $cfg['Servers'][$i]['AllowDeny']['rules'] 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 .htaccess 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).

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.