We have a universe that is used for ad-hoc reporting only, no standard reports. The problem is that we want each user of the universe to only be able to pull info for the location they belong to. We have a table that associates their BusinessObjects User ID and their location. I’m not sure how to build this security into the universe since we can’t build it into the reports as they are all ad-hoc. I thought maybe a strategy would work but I am new to strategies so I am not sure.
You’ll have to open each measure. When you look at the dialog you’ll see a Tables button. Click on that. Then select (ztrl-click) the table that you use to enforce security. Business Objects will then force a join to that table whenever that measure is selected. The same works for objects. Unfortunately, you have to do this for each one.
If the table is not directly joined, you may have to include the other tables in the path.
In a message dated 98-06-26 10:43:15 EDT, you write:
We have a universe that is used for ad-hoc reporting only, no standard
reports. The problem is that we want each user of the universe to only be able to pull info for the location they belong to. We have a table that associates their BusinessObjects User ID and their location. I’m not sure how to build this security into the universe since we can’t build it into the reports as they are all ad-hoc.
Maria:
How complicated (ie how many tables) is your universe? There are several ways to do table-based security in a universe; the best choice depends on a variety of factors. The following are presented in “random order” (ie as I thought of them I wrote them down… )
If the “location” code is in each table, then you can use Designer to add a join to each table based on @variable(‘BOUSER’). Every time a table is referenced the additional code would be added to the SQL.
You can use Supervisor to add a Row constraint on the table in much the same way; I would suggest using Designer as it is more efficient. Anything done in Supervisor is treated as an “override” and has additional overhead. Anything done in Designer is considered part of the base universe.
You could create views combining the base tables with the security tables (join on location code). Use the combined information to show users only the rows that they are authorized to see.
You can create separate views for each location. Build a different database connection for each set of views. Use the Supervisor application to remap the universe connection to an appropriate “location” connection based on the user login.
How many tables need to be driven by this type of security? How many users are there? How many different locations? All of these issues would help figure out which is the best solution.
Regards,
Dave Rathbun
Integra Solutions www.islink.com See you in Orlando in '98!
You can use Row Security based on the user or on a group.
Simply double-click on the universe in the Universe tab of the Supervisor while a group or user is selected. Then activate the Rows tab and create a where clause for the selected user or group. This where clause will then be appended to the SQL generated by the Reporter module.
If this method is chosen, remember to disallow users from editing the SQL in the Query Panel.
Robert
Schmidt Interactive Software, Inc.
We now post Document and ReportScript examples!!
Hi Everyone!!
We have a universe that is used for ad-hoc reporting only, no standard reports. The problem is that we want each user of the universe to only be able to pull info for the location they belong to. We have a table that associates their BusinessObjects User ID and their location. I’m not sure how to build this security into the universe since we can’t build it into the reports as they are all ad-hoc. I thought maybe a strategy would work but I am new to strategies so I am not sure.