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

Resolve additional aspects of multiple security databases from services and cross-database requests POV [CORE3370] #3736

Closed
firebird-automations opened this issue Mar 2, 2011 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Jira_subtask_inward CORE3368

Currently one can execute cross-database query on the same server without additional authentication. This was OK when having only server-wide authentication. With SecurityDatabase parameter, added to aliases.conf, one can login to some database as USER1, but it does not mean that he is granted to access as USER1 another database, for which another SecurityDatabase is psecified. Same issue with access to database using services.

Solution of this problem is supposed to go together with mapping server/OS security objects to database users. For services we need additional SPB parameter, specifying with what database are we going to work.

Commits: a0ddc67 20e8463 FirebirdSQL/fbt-repository@e4352dc FirebirdSQL/fbt-repository@fc6d00f

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Beta 1 [ 10332 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

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

No branches or pull requests

2 participants