Skip to content
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

Allow non-SYSDBA users to monitor not only their current attachment but other their attachments as well [CORE2233] #2660

Closed
firebird-issue-importer opened this issue Dec 10, 2008 · 10 comments

Comments

@firebird-issue-importer

Submitted by: @dyemanov

Is related to QA228

By the original design, non-privileged database users are allowed to see only their own attachment information inside the monitoring tables. It has been requested to allow them to see other attachments authenticated using the same user name.

Commits: ca0df9c 25dc79d

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

Implemented using test_type = 'ISQL'.
Main idea: run execute statement on EXTERNAL datasource and specify every time
different ROLE (no matter is that role exists or no - new connection always will be
etsblished and will be provided with new attachment_id in mon$attachments).

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2008

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2008

Modified by: @dyemanov

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2008

Commented by: Claudio Valderrama C. (robocop)

Not sure this is a good idea if there's middleware that logs in multiple times with the same user, but the end user is different.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2008

Commented by: @dyemanov

In the worst case (middleware works with SYSDBA or DBO permissions) this issue exists since v2.1.0. Maybe the middleware should not expose the monitoring features to the end user in this case?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 11, 2008

Modified by: @dyemanov

Fix Version: 2.1.2 [ 10270 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 12, 2008

Modified by: @dyemanov

status: In Progress [ 3 ] => Open [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 12, 2008

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 26, 2008

Modified by: @pmakowski

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 26, 2009

Modified by: @pcisar

Link: This issue is related to QA228 [ QA228 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 28, 2015

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully

Test Details: Implemented using test_type = 'ISQL'.
Main idea: run execute statement on EXTERNAL datasource and specify every time
different ROLE (no matter is that role exists or no - new connection always will be
etsblished and will be provided with new attachment_id in mon$attachments).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants