Relational Database Security Broker |
![]() ![]() ![]() |
The Relational Database Security Broker can be used to access and maintain the security information stored in all types of relational databases as long as there is proper JDBC driver for the database system. Although database systems mostly conform to SQL'92 standards still there exists vendor specific implementations that makes it difficult to process them in a standard way. Therefore the RelDB Security Broker uses SQL Patterns to solve the differences between the database systems. Using SQL patterns provides a flexible way of accessing the stored security information. Broker SQL Pattern Files The available Broker SQL Pattern files are located under {APPLICATION_PATH}/WEB-INF/MM-INF/config/security/bsp directory.
How a BSP File Structured? BSP files contains a standard set of SQL Patterns that are identified by Pattern Names. For example when the RelDB Security Broker wants to retrieve the information of a check point from the database it uses the "#Get CheckPoint Info By Name" pattern. The @{} symbols in the SQL patterns are resolved with their values before the SQL is executed through the JDBC driver.
The RelDB Security Broker has no idea of which tables and which columns are accessed. It only knows the type of the SQL query; It is either an update query that updates the database or a normal query that produces a result set. The @{} Symbols that can be used in SQL Patterns
See Customizing A Broker SQL Pattern File
|