Part 3: Implementing Security in BusinessObjects Universes with Security Tables
- by Taha M. Mahmoud, Senior BI Consultant
- March 21, 2017
Learn how to implement security in SAP BusinessObjects Universes using database security tables. Learn how to establish and create database security tables, store security information in those tables, import the tables into your Universe, and join the tables with your current Universe model by joining them with the corresponding tables in the Universe. Finally, find out the main differences between using the Information Design Tool security editor and using database tables to implement security in a Universe.
By reading this article you will learn:
- How to define security database tables
- How to apply security on the Universe level using two enterprise security tables
- What the main difference is between using the security editor and using security database tables
Enterprise security database tables are normal database tables that store security information (such as user name) and the corresponding database keys to the information that users can see. Security tables are used inside the Universe and are linked with the original database tables. When users log in and try to display information in any SAP document, such as a Web Intelligence report, dashboard, or SAP Lumira visualization based on this Universe, they are only able to see information granted to them.
Security is a very important topic in the world of business intelligence (BI). In part 1 of this three-part series of articles, I introduced the different security levels in the SAP BusinessObjects BI platform: object level, application level, and Universe level.
Part 2 of this series explained the two approaches to implementing security inside Universes—using enterprise database security tables and the security editor—and provided details for how to use the security editor to do this. As discussed previously, there are two main approaches for implementing security in an SAP BusinessObjects Universe:
- Using the SAP BusinessObjects Information Design Tool (IDT) security editor (discussed in detail in part 2 of this series)
- Using enterprise database security tables (the main topic of this article)
The first approach (using a security editor) is a built-in feature and it can be used to create different categories of security profiles that can then be assigned to the corresponding user or group. This option provides a graphical user interface (GUI) for creating profiles and assigning users. I recommend that you use this method if you want to implement customized security profiles tailored per Universe and you are not planning to use them in other Universes.
In this final article of this three-part master-guide series, the focus is on how to use the second option for applying security inside SAP BusinessObjects Universes—using enterprise database security tables. I recommend that you use this option if you want to re-use your security assignment in other BI tools or if you want to re-use it in more than one Universe (ergo the term enterprise). Using this method, you need to define security just one time and then you can use the same security tables with different Universes and subject areas.
In this article, you learn about:
- How to implement security in the Universe using enterprise security database tables
- The main differences between implementing security using the IDT security editor and using enterprise database security tables
Configuring security profiles in a Universe enforces the implemented security rules (e.g., applying some filters that can’t be changed by the end users on whom the filters are applied) on all BI artifacts based on this Universe, such as Web Intelligence reports, Crystal Reports, dashboards, SAP BusinessObjects Lumira visualizations, SAP BusinessObjects Design Studio dashboards, and mobile BI documents (reports and dashboards).
Would you like to see this full item?