Submitted by: Michael Trowe (bubble76)

Is duplicated by CORE645
Is related to QA106

SFID: 1461705#⁠
Submitted By: bubble76

I think it would be useful to have triggers for
database-wide events.
Like:
AFTER LOGIN
BEFORE LOGOUT
AFTER TRANSACTION_START
BEFORE TRANSACTION_COMMIT

With this you can create a session-log or set
predefined contextvalues (rdb$set_context).
And in case that an exception in AFTER LOGIN breaks the
connection you can do an additional user verification.
e.g. check if the login for the user is allowed from
rdb$get_context('SYSTEM', 'CLIENT_ADDRESS').
And it brings one kind of lowlevel-security: You can
prevent that it is possible to connect to the database
on a server where the SYSDBA password is known. Ok -
it's pseudo security as long as the database isn't
crypted, and everyone can build it's own fb-version
ignoring this triggers. But in some cases it's enough.

Commits: 570b6cd

====== Test Details ======

See:
functional\trigger\database\transaction_*.fbt
functional\trigger\database\connect_*.fbt