New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add field in SEC$USERS reflecting whether a user has RDB$ADMIN role in security database [CORE4469] #4789
Comments
Commented by: Sean Leyne (seanleyne) Why is this necessary? Can't you query to the User_Role data to determine that? |
Commented by: Robert (rjm1102) Hi Sean. |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff To be precise almost everything regarding rdb$admin is still broken. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Beta 1 [ 10332 ] |
Commented by: @pavel-zotov Was this request really implemented ? SQL> create user boss password '123'; commit; SEC$USER_NAME BOSS SQL> grant rdb$admin to boss; SEC$USER_NAME BOSS PS. LI-T3.0.0.31797 |
Commented by: @AlexPeshkoff # ./isql employee SEC$ADMIN<false> SQL> alter user boss grant admin role; SEC$ADMIN<true> SQL> |
Submitted by: Robert (rjm1102)
I like to request a new field in SEC$USERS that reflects whether a user has the RDB$ADMIN role in the security database (as a result of CREATE USER GRANT ADMIN ROLE).
Suggested names for this new field: SEC$ADMIN_ROLE or SEC$ADMIN, value 0/1 or boolean.
This is the only user info missing now in sec$users, that can be obtained by the service manager (isc_action_svc_display_user_adm).
Note: special consideration is needed for user SYSDBA because this user is of course an administrator, but has not the RDB$ADMIN role been assigned in the security database. I suggest to assign 0 for this user to the new field because this is also the case for fbsvcmgr action_display_user_adm.
Commits: adb0480 FirebirdSQL/fbt-repository@2a4e70e
The text was updated successfully, but these errors were encountered: