firebird/firebird-mirror
firebird/firebird-mirror
8
0
Fork 1
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-22 18:43:02 +01:00
Code Issues

Added readme for trusted authentication in windows

Browse Source
This commit is contained in:
alexpeshkoff 2007-04-11 15:34:32 +00:00
parent 6f571ee4a1
commit 492d58a7a2
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
doc/README.trusted_authentication Normal file
View File

@ -0,0 +1,31 @@
New way to authenticate users in firebird 2.1.
Firebird starting with version 2.1 can use windows security for user authentication. Current security context is passed to the server and if it's OK for that server is used to determine firebird user name. To use windows trusted authentication, do not put user and password parameters in DPB/SPB. This will automatically lead to use of trusted authentication in almost all cases (see environment below for exceptions). Suppose you have logged to the windows server SRV as user John. If you connect to server SRV with isql, not specifying firebird login and password:
isql srv:employee
and do:
select CURRENT_USER from rdb$database;
you will get something like:
USER
===============================================================================
SRV\John
Windows users may be granted rights to access database objects and roles in the same way as traditional firebird users. (This is not something new - in UNIX OS users might be granted rights virtually always).
If member of Domain Admins builtin group connects to firebird using trusted authentication, he will be connected as SYSDBA.
New parameter is added to firebird.conf - it is used to select available authentication method. Parameter is called Authentication and may have values Native, Trusted and Mixed. Default is mixed authentication. Using native method you get full compatibility with previous firebird versions, avoiding trusted authentication. In trusted-only case security database is ignored and only windows authentication is used (in some aspects this is the most secure way, i.e. it is exactly as secure as host OS).
To keep legacy behavior when ISC_USER/ISC_PASSWORD variables are set in environment, they are picked and used instead of trusted authentication. In case when trusted authentication is needed when ISC_USER/ISC_PASSWORD are set, add new DPB parameter isc_dpb_trusted_auth to DPB. In most of firebird command line utilities switch -trusted (may be abbreviated up to utility rules) is used for it. Exceptions for today are qli (it uses single-letter switches, switch of interest is -K) and nbackup (also has single-letter switches, force of trusted authentication over environment is not implemented yet). Example:
isql srv:db -- log using trusted authentication
set ISC_USER=user1
set ISC_PASSWORD=12345
isql srv:db -- log as 'user1' from environment
isql -trust srv:db -- log using trusted authentication
Author: Alex Peshkov, peshkoff@mail.ru