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
Unable to connect with database if security.db reference is removed from databases.conf file [CORE6230] #6474
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff Why did you not provide a comment from databases.conf before mentioned section: # If you really need to remove security.db from databases.conf just add |
Modified by: @AlexPeshkoff |
Commented by: @AlexPeshkoff There is no correct dependency in the tracker - CORE6230 _conflicts_ with CORE6072. With explicit (not alias) name of default security database use of multiple providers is impossible. |
Commented by: @luronumen Hi Alexander Peshkov, This issue was raised first because it did not happen in the previous Firebird version (3.0.4) and second because good software practices suggest that configuration files be used to modify the default software behavior but not to setup everything. An example of this is the Firebird port configuration itself where if the user does not set it in Firebird.conf then port 3050 is automatically used. Beside that, it would be important that the databases.conf file had a high backward compatibility with the old aliases.conf file facilitating migration from version 2.5 to version 3.0. Based on your comment I believe the best solution for this issue would be for Firebird to consider "SecurityDatabase = $ (dir_secDb) /security3.fdb" every time it finds no reference to it in the firebird.conf and databases.conf files. Best Regards, |
Commented by: @luronumen Retest result on Firebird 3.0.5.33220 (Official Firebird 3.0.5): - FAILED (#motorolablocker) |
Commented by: @AlexPeshkoff Have you seen it's marked as fixed? Why do you expect other result? ;) Getting serious we have 2 options. I still do not know what is less evil. |
Commented by: @luronumen Hi Alexander Peshkov, Thank you very much for your prompt reply! Best Regards, firebird.conf |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] Fix Version: 3.0.6 [ 10889 ] |
Submitted by: @luronumen
Block progress on CORE6072
ACTUAL RESULT
- Unable to connect with any database if security.db reference is removed from databases.conf file
- <I/O error during "CreateFile (open)" operation for file "security.db"> error message is displayed when is trying to create or alter users (e.g.: CREATE OR ALTER USER SYSDBA SET PASSWORD 'blablabla' USING PLUGIN LEGACY_USERMANAGER;
EXPECTED RESULT
- The Firebird engine should consider the $(dir_secDb)/security3.fdb as your default security.db when it is not included on databases.conf file;
- The end user should be able to connect with any database security.db reference is not on databases.conf file;
- No error should be happen when is trying to create or alter users;
IMPORTANT NOTES:
- This issue did NOT happen with the Firebird 3.0.4 (Regression issue)
===Default security.db reference from databases.conf file===
security.db = $(dir_secDb)/security3.fdb
{
RemoteAccess = false
DefaultDbCachePages = 50
}
Commits: d39f26a 53faf9e
The text was updated successfully, but these errors were encountered: