Is this one still reproducible? I performed the following test:

Prerequisites:¶

- MAMP environment with MAMP Pro (PHP 7.1.12, MySQL 5.6.38)
- Fresh installation of TYPO3 8.7.13

Test procedure:¶

- I created an empty database called "typo3test2"
- I created a database user called "typo3test2" and granted him the privileges as shown on the attached files
- I started the usual TYPO3 installation (manual installation with symlinks);

Results:¶

- When choosing the database, I was able to choose only typo3test2 (see attached Schermata 2018-05-18 alle 23.27.29.png)
- No error has been encountered, the installation has been successful.

I admit I am not expert in DB administrator, so is there a different test that should be performed? Or under different conditions?

@Johannes Schmidt

Thank you for your bug report. It would be really helpful in the future if you also provide some steps to reproduce for errors like these.

The less time it takes to try to reproduce issues, the more likely the bug is to get fixed.

I could reproduce it with the following:

Reproduce¶

System¶

• TYPO3 9.3-dev (it is very probable that it is also reproducable with current 8.x version)
• MySQL Server version: 5.7.22-0ubuntu0.16.04.1 (probably not relevant)

Steps to reproduce¶

1. Setup database and database permission in DB server

mysql> CREATE database db CHARACTER SET utf8 COLLATE utf8_general_ci;
mysql> CREATE USER username@localhost identified by 'password';
mysql> GRANT SHOW DATABASES ON *.* TO username@localhost;
mysql> GRANT ALL ON db.* TO username@localhost;

2. Start installation ...

Result:¶

Couldn't select existing database and got exception:

Exception
An exception occurred in driver: Access denied for user 'typo3'@'localhost' to database 'redmine_default'

General observations¶

But another thing: Why would you want to give a Database User for TYPO3 show databases privileges to all databases?

In my opinion this makes no sense at all and is not to be recommended. It's not required for TYPO3 and for reasons of security it is best to give only access that is required and nothing more. Even though in this particular case it does no harm but why would you do it?

Summary¶

I can reproduce it, and it is a bug and I agree it should be fixed, but I would give it low priority, because it can only be reproduced by doing things you should not be doing anyway.

quote: "The only solution right now is to give the database user full access privileges for all databases — which works but surely isn't a viable solution."

No, a better solution is to not give TYPO3 user access to `show databases` in the first place or when you get the exception while installing you can revoke it:

mysql>revoke show databases on *.* from user@localhost;

If I then reload the page with the exception, I can select the correct database and continue with the installation. This works for TYPO3 9.3-dev. Hopefully it works for TYPO3 8 too.

I lower the priority for now; adjust it or ping me if this is the wrong decision

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64564

Applied in changeset 3d9931531a3eabfd02097afcfe695e63f3564e8f.