Menu

#4629 (ok 4.3.2) Problem with custom SQL queries using cookie authentication

4.3.1
fixed
None
1
2014-12-12
2014-12-09
No

I have recently upgraded my phpMyAdmin installation from 4.2.13 to 4.3.0 and now 4.3.1, but with both newer versions custom SQL queries seem to be broken (with auth_type cookie):
I either get a token mismatch warning when I enter a custom SQL query and select OK, or nothing happens at all. When I select a different menu (like Export) afterwards, I get disconnected and have to log in again.
This only happens wehen I enter a custom SQL query, if I select a table in the left menu and then select SQL in the top menu and click OK, then the predefined query is executed without errors. However, if I modify the query, then the error usually occurs again.

Discussion

  • Madhura Jayaratne

    Did you clear you browser cache after updating to newer version?
    What is your browser? Do you get this issue on other browsers as well?

     
  • Tobias Grave

    Tobias Grave - 2014-12-09

    I used Firefox and Google Chrome, clearing the browser cache did not help.

    I have also tried different server setups:
    Ubuntu 12.04: Apache 2.2 with PHP 5.3 (mod_php)
    Ubuntu 14.04: Apache 2.4 with PHP 5.5 (PHP-FPM)
    Both show the same errors.

    MySQL Server version: 5.5

     

    Last edit: Tobias Grave 2014-12-09
  • Pierre Gasté

    Pierre Gasté - 2014-12-09

    Same problem here.
    I'm using PMA with multiples servers. When I execute a query on the default server, there is no problem at all. But, with another server, I have the same problem (token mismatch).

    When I change the default server (in the config.inc.php file), the default server doesn't have the "token mismatch" problem.
    I clear my browser cache (Chrome), try in the private navigation mode (I do the same with Firefox) : still the same issue.

    • PMA 4.3.1 with 6 servers
    • MySQL 5.6.
     

    Last edit: Pierre Gasté 2014-12-09
  • Pierre Gasté

    Pierre Gasté - 2014-12-09

    To solve it (because I'm behind a firewall), I comment the line 476 in the file common.inc.php to disable the token system...
    Line 476, I replace :

    $token_mismatch = false;
    

    Note that it's a temporarily and unsecured workaround.

     

    Last edit: Pierre Gasté 2014-12-09
  • Tobias Grave

    Tobias Grave - 2014-12-09

    I also use multiple servers.

    When I switch to a single server configuration the error seems to be gone.

     
  • Madhura Jayaratne

    • assigned_to: Madhura Jayaratne
     
  • Madhura Jayaratne

    • summary: Problem with custom SQL queries using cookie authentication --> (ok 4.3.2) Problem with custom SQL queries using cookie authentication
    • status: open --> resolved
    • Priority: 5 --> 1
     
  • Marc Delisle

    Marc Delisle - 2014-12-12
    • Status: resolved --> fixed