Firebird Documentation IndexFirebird 3.0.2 Release NotesCompatibility Issues → Legacy Authentication
Firebird Home Firebird Home Prev: Initializing the Security DatabaseFirebird Documentation IndexUp: Compatibility IssuesNext: Upgrading a v.2.x Security Database

Legacy Authentication

If you do not intend to use SRP encrypted log-ins right away and want to use the security database—security3.fdb— as you have done in previous Firebird versions, proceed as follows:

  1. Using a text editor, open firebird.conf and find the entry for the parameter UserManager:

      #UserManager = Srp
              

    Delete the “#” symbol and change the value to:

      UserManager = Legacy_UserManager
              
  2. Find the entry for the WireCrypt parameter:

      #WireCrypt = Enabled (for client) / Required (for server)
              

    Delete the “#” symbol and change the value to:

      WireCrypt = Enabled
      -- or, if you don't plan to use SRP encryption at all --
      WireCrypt = Disabled
              
  3. Find the entry for the AuthServer parameter:

      #AuthServer = Srp, WinSspi, Legacy_Auth
              

    Delete the “#” symbol and change the order of the arguments:

      AuthServer = Legacy_Auth, Srp, WinSspi
              
  4. Find the entry for the AuthClient parameter:

      #AuthClient = Srp, WinSspi, Legacy_Auth
              

    Delete the “#” symbol and change the order of the arguments:

      AuthClient = Legacy_Auth, Srp, WinSspi
              
  5. Save the changes.

  6. Stop and restart Firebird for the changes to take effect.

Legacy Passwords

  • The old masterke password is available for your first login as SYSDBA. It is known to the whole world and should be changed as soon as possible.

  • Reminder: Legacy authentication reads only the first 8 characters of any password.

Prev: Initializing the Security DatabaseFirebird Documentation IndexUp: Compatibility IssuesNext: Upgrading a v.2.x Security Database
Firebird Documentation IndexFirebird 3.0.2 Release NotesCompatibility Issues → Legacy Authentication