[go: nahoru, domu]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

4.7.0 using logged in user to access pma__tracking table. #13132

Closed
James-Oakley opened this issue Mar 30, 2017 · 5 comments
Closed

4.7.0 using logged in user to access pma__tracking table. #13132

James-Oakley opened this issue Mar 30, 2017 · 5 comments
Assignees
@nijel
Labels
Bug A problem or regression with an existing feature
Milestone
4.7.1

Comments

@James-Oakley
Copy link

Steps to reproduce

  1. Log in to phpMyAdmin as a non-root user who is not the control user for phpMyAdmin itself
  2. Run any update query.

Expected behaviour

The update query should run, as appropriate.

Actual behaviour

In addition, an error is displayed:

"Error: #1142 SELECT command denied to user '{logged-in-user}'@'localhost' for table 'pma__tracking'"

In other words, phpMyAdmin is trying to perform an operation on the pma__tracking table as the user logged in to phpMyAdmin, instead of using the control user to perform the operation.

I have a control user set up, and everything in config.inc.php is correct AFAIK - at least, this issue is new to my installation since I upgraded to 4.7.0 from 4.6.x

Server configuration

Centos 7.3.1611

Web server:
Apache 2.4.6

Database:
MariaDB 10.1.22

PHP version:
7.1.3

phpMyAdmin version:
4.7.0

Client configuration

Browser:
Firefox 52.0.2

Operating system:
Windows 10 x64
phpma-error-20170330
@silverasu
Copy link

Can confirm. PMA controluser does not always use controluser connection. For example, while inserting new row.

@nijel nijel added the Bug A problem or regression with an existing feature label Mar 30, 2017
@nijel nijel added this to the 4.7.1 milestone Mar 30, 2017
@nijel nijel self-assigned this Mar 30, 2017
@nijel nijel closed this as completed in cf525c7 Mar 30, 2017
@felixbuenemann
Copy link

@nijel Is there an estimated release date for 4.7.1? The STABLE branch is severely broken without this fix.

@ibennetch
Copy link
Member

@felixbuenemann 4.7.1 is expected in the middle of May.

@felixbuenemann
Copy link

@ibennetch Thanks for the info.

Would it be possible to get this fix merged to STABLE ahead of the 4.7.1 release?

@nijel
Copy link
Contributor
nijel commented Apr 28, 2017

STABLE is defined as last released version, so it's not possible without release.

This was referenced May 4, 2017
Closed
Closed
@boutilpj boutilpj mentioned this issue May 18, 2017
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@nijel nijel

Labels
Bug A problem or regression with an existing feature
Projects
None yet
Milestone
4.7.1
Development

No branches or pull requests
5 participants
@nijel @felixbuenemann @ibennetch @James-Oakley @silverasu