Today I though I'd give Firebird 3.0 a shot, but for some reason I can't seem to get it installed - at least not in a way that I can connect from a JDBC application.

What I did was to follow this article. This is what happened:

c:\etc\Firebird30>gsec -add sysdba -pass masterkey

c:\etc\Firebird30>start firebird.exe -a -m

Use CONNECT or CREATE DATABASE to specify a database
SQL> create database "localhost:c:\temp\mydbfb3.fdb" user "sysdba" password "masterkey";
Statement failed, SQLSTATE = 08006
Error reading data from the connection.

Now creating the database "locally" works:

SQL> create database "c:\temp\mydbfb3.fdb" user "sysdba" password "masterkey";
SQL> commit;

But in that case, when I connect from a JDBC application (still everything "localhost"), I get the error message (using sysdba/masterkey to log in)

GDS Exception. 335544472. Your user name and password are not defined. Ask your database administrator to set up a Firebird login.
Reason: Your user name and password are not defined. Ask your database administrator to set up a Firebird login.

I double-checked (more than once) that the username and password in the JDBC application is sysdba/masterkey.

From the commandline I can indeed access that newly created database:

SQL> connect 'c:\temp\mydbfb3.fdb';
Database:  'c:\temp\mydbfb3.fdb'
SQL> create table foo  (bar integer);
SQL> insert into foo values (1);
SQL> select * from foo;


SQL> commit;

I'm sure I'm missing something obvious, but what?

1 Answer 1


The problem is twofold:

First, Firebird 3.0 uses tighter security and has the old authentication mechanism disabled by default. So, clients depending on older connection libraries will not work out of the box.

To allow the old authentication mechanism to work, the following setting needs to be set in firebird.conf:

AuthServer = Legacy_Auth, Srp, Win_Sspi

(be sure to remove the # prefix)

Second, the pure Java wire protocol implementation of Jaybird (the Firebird JDBC driver) in version 2.2 and earlier uses an outdated authentication mechanism that is not supported by this Legacy_Auth option. Using Jaybird to connect to Firebird 3.0 at this time will only work if you use the native option (with the jdbc:firebirdsql:native: URL-prefix and jaybird2x.dll and fbclient.dll).

Addendum 1

Firebird 3.0 (since Alpha 1) has now also implemented the old authentication method used by Jaybird, so Jaybird will now also work without using the native library (as long as the legacy authentication is enabled, and the user has been setup with the legacy usermanager).

See also Jaybird and Firebird 3

Addendum 2

Jaybird 3 and higher support the more secure Srp authentication model out of the box, and Jaybird 3.0.4 introduced support for the wire protocol encryption. This means that it can connect to Firebird 3.0 without additional configuration.

  • Thanks. I will wait until the final version of Firebird and Jaybird is released.
    – user1822
    Commented Apr 18, 2012 at 20:24
  • 1
    Although I don't understand why I cannot connect using isql. using localhost:mydb (where mydb is an existing alias). The isql tool that comes with FB 3.0 should support the new authentication mechanism, shouldn't it? (I did change the AuthServer as you recommended)
    – user1822
    Commented Apr 18, 2012 at 22:10
  • I am not sure what is causing the problem. Can you file a ticket at tracker.firebirdsql.org ? Commented Apr 19, 2012 at 17:25
  • Where you by any chance running another Firebird instance as well? Commented Apr 19, 2012 at 17:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.