Commented by: @AlexPeshkoff

There are 2 cases, where previously #⁠ifdefs worked:
1. No username/password in DPB, and environment is analyzed for ISC_USER/ISC_PASSWORD.
2. No username/password in DPB in services - on posix OS authentication is used, therefore making (for example) restored database owned by SYSDBA if server is started with root run-user.

Currently we may solve some of the issues with #⁠ifdef, but since 3.0 with OSRI architecture - it's impossible. To make code know exactly is it invoked embedded or in network server, the simplest way is to analyze isinfromation about network address, from which connection is made, present in DPB. But to make it work with services, we also need to pass it to servcies from service manager. It's also useful if one wants to track for remote IP in (imaginable) trigger in RDB$USERS table, which should store IP from which record was last changed.

Commented by: @dyemanov

I don't see the bug description mentioning either the "wrong" auth mode or the "expected" one. So, what was the problem you attempted to fix? :-)

Commented by: @AlexPeshkoff

1. It's wrong that server accepts environment variables for any remote connection without isc_dpb_user/password tags.
2. It's wrong that (in posix only) server uses OS auth for connection(s) without isc_dpb_user/password tags.