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

User 'otobo' has access denied to DB during or after running installer.pl #2056

Closed
bschmalhofer opened this issue Dec 20, 2022 · 1 comment
Closed
Assignees
Labels
bug Something isn't working as intended installation Concerning the installation of OTOBO
Milestone

Comments

@bschmalhofer
Copy link
Contributor

When running installer.pl the user 'otobo' is created in the database and the credentials are stored in the module file Kernel/Config.pm . But when running installer.pl we get an error "Access denied". This seems to indicate that Kernel/Config.pm is not reloaded after it has been writter to disk. After some fiddling @svenoe found out that this effect goes away after S3 support has been removed from bin/psgi-bin/otobo.psgi . The assumption is that loading Kernel::Config in otobo.psgi effects that on old version of Kernel::Config stays around, which does not have the correct credentials.

@bschmalhofer bschmalhofer added bug Something isn't working as intended installation Concerning the installation of OTOBO labels Dec 20, 2022
@bschmalhofer bschmalhofer added this to the OTOBO 10.1.6 milestone Dec 20, 2022
@bschmalhofer bschmalhofer self-assigned this Dec 20, 2022
bschmalhofer added a commit that referenced this issue Dec 20, 2022
in the initial process that spawns the workers.
Because it is not guaranteed that a changed file Kernel/Config.pm
forces a reload of Kernel::Config.
bschmalhofer added a commit that referenced this issue Dec 20, 2022
…denied

Issue #2056: make sure that Kernel::Config is not loaded
@bschmalhofer
Copy link
Contributor Author

For reactivating S3 support in bin/psgi-bin/otobo.psgi it should suffice to registerter Kernel/Config.pm before $S3Active is checked. Calling Kernel::System::ModuleRefresh::update_cache() should guarantee that $ModuleRefreshMiddleware does indeed reload a changed config when the middleware runs for the first time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended installation Concerning the installation of OTOBO
Projects
None yet
Development

No branches or pull requests

2 participants