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.

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

Underscores in DB backend names not working #5204

Closed
akellar opened this issue Mar 29, 2024 · 2 comments
Closed

Underscores in DB backend names not working #5204

akellar opened this issue Mar 29, 2024 · 2 comments
Labels
no-issue Better asked in one of our support channels

Comments

@akellar
Copy link

akellar commented Mar 29, 2024

Describe the bug

When using MariaDB database back end, underscores in DB names result in the Icingaweb2 application not properly accessing the DB, even though underscores are permitted in DB names by MySQL/MariaDB (provided they don't begin with an underscore).

To Reproduce

I have a live example here in community forums, if you need more troubleshooting steps or more information please let me know.
https://community.icinga.com/t/setting-up-icinga-web-db-for-local-auth-cannot-access-db/13349

Expected behavior

IcingaWeb2 be able to access a MariaDB database authentication back end with an underscore in the DB name.

Screenshots

Screenshots and clear examples shown in link provided in "To Reproduce" section.

Your Environment

Debian 12 Bookworm environment, single master all databases on localhost (had tried a remote MariaDB server as well - experienced same issue)

  • Icinga Web 2 version and modules (System - About): 2.12.1
  • Web browser used: Firefox and Brave
  • Icinga 2 version used (icinga2 --version): r2.14.2-1
  • PHP version used (php --version): 8.2.7
  • Server operating system and version: Debian 12 Bookworm

Additional context

Detailed context and examples provided in the link. Please let me know if you need anything else.

@nilmerg
Copy link
Member

nilmerg commented Apr 2, 2024

Hi,

please have a look here

@nilmerg
Copy link
Member

nilmerg commented Apr 2, 2024

Duplicate of #5147

@nilmerg nilmerg marked this as a duplicate of #5147 Apr 2, 2024
@nilmerg nilmerg closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
@nilmerg nilmerg added the no-issue Better asked in one of our support channels label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue Better asked in one of our support channels
Projects
None yet
Development

No branches or pull requests

2 participants