On 2017-03-01 09:59, Dmitry Yemanov dim...@users.sourceforge.net
[firebird-support] wrote:
> 01.03.2017 11:58, jonatan.laurit...@yahoo.dk wrote:
>
>> OK, I have working Firebird 3.0.1 installation and I have copied
>> security3.fdb from the broken Firebird installation and now I am also
>>
On 2017-03-01 11:41, jonatan.laurit...@yahoo.dk [firebird-support]
wrote:
> Solution found - I had to use the "create user" command with the
> "using" clause:
> SQL> create user SYSDBA password 'masterkey' using plugin Srp;
>
> My firebird.cong indicated that Legacy_Auth is the first (default)
>
Solution found - I had to use the "create user" command with the "using" clause:
SQL> create user SYSDBA password 'masterkey' using plugin Srp;
My firebird.cong indicated that Legacy_Auth is the first (default) user manager
and it was necessary for isql to know that Srp manager had to be used:
isql allowed to change the password of the SYSDBA account but that did not
removed original error message about "installation incomplete"...
OK - I am starting to understand. Apparently client had Firebird default
instance Windows registry entry from the Firebird installations of the previous
versions. That is why Firebird 3.0 installation wizard did not displayed
extended configuration form with the possibility to initialize
01.03.2017 11:37, jonatan.laurit...@yahoo.dk wrote:
> Actually, I don't understand this thing about old and new authorization
> system. Does it mean that there are two SYSDBA and other user accounts -
> one for old and other for new authorization system and does it mean that
> there are two sets
01.03.2017 11:58, jonatan.laurit...@yahoo.dk wrote:
> OK, I have working Firebird 3.0.1 installation and I have copied
> security3.fdb from the broken Firebird installation and now I am also
> receiving the error message. So - security3.fdb is somehow broken,
> problem is in security3.fdb
It's
OK, I have working Firebird 3.0.1 installation and I have copied security3.fdb
from the broken Firebird installation and now I am also receiving the error
message. So - security3.fdb is somehow broken, problem is in security3.fdb
Actually, I don't understand this thing about old and new authorization system.
Does it mean that there are two SYSDBA and other user accounts - one for old
and other for new authorization system and does it mean that there are two sets
of passwords?
Is it safe to check 'Enable authorization
