ALTER USER XXX INACTIVE [CORE2004] #2441
Comments
|
Commented by: @pmakowski With version 2.1 it is easy with ON CONNECT TRIGGER and database per database |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 2 [ 10560 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Sent letter to dimitr, alex, 09.03.2018 19:33. Waiting for reply. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Done with caveats Test Details: Sent letter to dimitr, alex, 09.03.2018 19:33. Waiting for reply. => Sent letters to dimitr and alex: Test was committed because it does some checks of ability to make user active/inactive. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Done with caveats => Done successfully Test Details: Sent letters to dimitr and alex: Test was committed because it does some checks of ability to make user active/inactive. => Sent letters to dimitr and alex:
|
Submitted by: Mercea Paul (m24paul)
Votes: 3
I would like to have the possibility to inactivate the user!This could preserve all right but not allow her/him to log in!
For version 3 could be inactivated just for database1 or 2...etc, and active for database 6 or 9 !
Commits: 64b4f89 FirebirdSQL/fbt-repository@84c5aa8
====== Test Details ======
Sent letters to dimitr and alex:
1) 09.03.2018 19:33.
2) 10.03.2018 16:00 (about need of granting rdb$admin role)
See also test for CORE5770
Test was committed because it does some checks of ability to make user active/inactive.
The text was updated successfully, but these errors were encountered: