On Wednesday, February 15, 2017 10:42:27 AM EST you wrote:

>
> All the workarounds I mentioned above work. Although for the second
> workaround it is actually necessary to create the user, just starting
> gsec is not sufficient.

I will look into those

> Another workaround is to change the AuthServer setting to only Legacy_Auth.

That did work! The first time I could connect using Jaybird 3. It did require
?lc_ctype=NONE&charSet=iso-8859-1

I did not try combos

> I have also created http://tracker.firebirdsql.org/browse/CORE-5485 to
> ask the Firebird developers to continue with the next plugin for these
> types of failures.
>
> I will also consider if I can move the introduction of a connection
> property to control the list of plugins to try and their order, to
> before the Jaybird 3 release.

Something that could be specified on the URL may help. Just for legacy, so
would not be normal for default/SRP.

> The error is a straight out failure, so it is not possible for Jaybird
> to continue with the next plugin on its own (using a Firebird 3
> fbclient.dll will exhibit the same behavior if it tries Srp first).

Could the order be reversed and try legacy then Srp? If Srp failure is causing
problems for Jaybird to try the next plugin. That may be another way to go,
although more ideal to use Srp first then legacy. May need to reverse for a
transition period.

I can see others doing legacy before srp, though some may go the opposite. I
get what your saying, since Srp, Legacy did not work for Jaybird 2 and
Flamerobin. If Srp fails and Legacy did not, it was not trying legacy just
failing to connect. Thus me having Legacy, Srp ordering.

--
William L. Thomson Jr.


[Non-text portions of this message have been removed]