You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: