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
New system table for user managemet [CORE1996] #2433
Comments
Commented by: Jorge Andres Brugger (jbrugger) Nobody should see other users passwords, even if he is the sysdba. |
Commented by: Sean Leyne (seanleyne) The visibility of a user list violates many standards regarding system security. Accordingly, it is likely that this case will be rejected. |
Commented by: Pabloj (pabloj_sourceforge) While I understand the comment about passwords I don't see why there shouldn't be a way of listing all users with a simple sql query. |
Commented by: Smirnoff Serg (wildsery) User privileges may be granted without user existance, and user may be without any privileges in this database. |
Commented by: Pabloj (pabloj_sourceforge) That's another use for rdb$users, it could show those existing users that don't have privileges on a specific database, joining with the rdb$user_privileges. |
Commented by: Smirnoff Serg (wildsery) No, I don't need to see this users from another database. |
Commented by: Pabloj (pabloj_sourceforge) If there is a plan, as it seems to be, to have a centralized user management then something like what I said is definitely useful, and implemented through a table is certainly better than through some special command or an external tool like gsec. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Pabloj (pabloj_sourceforge)
Duplicates CORE685
Duplicates CORE2639
Votes: 1
After adding support for CREATE USER etc. it would be nice to have a system table like RDB$USERS that lists all users and their respective passwords, first, middle and last names (of course only SYSDBA should be able to see the password column).
The text was updated successfully, but these errors were encountered: