Yes it is possible, but in the server's firebird.conf
1) AuthServer (not ServerAuth) must include Legacy_Auth (preferably
*after* the more secure authentication plugins), e.g.
AuthServer = Srp256, Srp, Legacy_Auth
2) WireCrypt must be set to Enabled (or Disabled, but use of Enabled is
preferred so you don't remove encryption for clients that do support
it); the default is Required (which is what causes your current error), so:
WireCrypt = Enabled
3) You need to add Legacy_UserManager to UserManager, so:
UserManager = Srp, Legacy_UserManager
If UserManager is currently commented out, or explicitly configured to
Srp, *do not* add Legacy_UserManager first, and *do not* remove Srp, as
that will lower security as unqualified user management statements
(without USING PLUGIN) and deprecated gsec will then manage less secure
legacy users by default, and it could break things (like listing all
users, or users managing their own password)
4) You must create a user using this legacy user manager:
create user THE_USER password 'thepassword' using plugin Legacy_UserManager;
A user created with Srp cannot be authenticated by an old client (users
exist per user manager).
The setting AuthClient (not ClientAuth) is not involved at all (it
essentially configures the server as client, and other applications in
the Firebird installation).
See also the instructions I wrote for Jaybird 2.2 (which basically had
the same limitations as the Firebird 2.5 or older fbclient.dll):
https://github.com/FirebirdSQL/jaybird/wiki/Jaybird-and-Firebird-3#jaybird-22-and-earlier
Mark
--
Mark Rotteveel