MicroStrategy has a robust security model that enables you to create users and groups, determine how they are authenticated, control what data they can see, and what functional privileges they can have. For detailed information, please refer to the MicroStrategy System Administration Guide. This section discusses the Access Control List (ACL) and security filters that relate to Freeform SQL reports only.
Access control list
An access control list (ACL) is a list of users and groups and the access permission that each one has to objects in aMicroStrategy project. Different users may have different permissions on the same object.
When you use existing objects (including project objects) in column mapping, the ACL of these objects remains. However, new objects (attributes and metrics) created in Freeform SQL reports inherit the ACL from what is defined as default in the Project Configuration Editor (Project Configuration -> Project definition -> Security -> Access control -> Set Freeform SQL and MDX objects default security). When you click Modify, the Properties [XDA Objects] dialog box is displayed. The Permissions list has the following settings:
In addition, whoever creates the new objects (attributes, metrics) has the Full Control permission.
In the Properties [XDA Objects] dialog box, you can change the settings of the default ACL for different groups of users. However, note that the changed settings will only affect the new objects (attributes and metrics) created subsequently in Freeform SQL reports, but not those objects created prior to the change.
A security filter is a filter object that is used to narrow down the result set that users or groups obtain when they execute reports or browse elements. Usually assigned by Administrators, security filters control, at the MicroStrategy level, what warehouse data users can see.
A security filter has three components that are defined by Administrators:
As for regular reports in MicroStrategy, security filters can also be applied to Freeform SQL reports. Actually, a security filter for a Freeform SQL report is not much different from that for a standard report. The same concepts still apply.
If you use an older version of MicroStrategy prior to 8.0, make sure that you run the project update for the metadata; otherwise, the security filter functionality will not be applied to Freeform SQL reports.
By default, Freeform SQL reports do not take into account security filters. The Report Designer has to insert a security filter placeholder in a Freeform SQL report and configure it; otherwise, any user can run the report without being limitedin the data he or she sees.
Because the SQL statement is static, a security filter string (“where Security Filter” or “and Security Filter”) needs to be manually embedded into the statement, such as the following:Select Year_ID, Store_ID, M1 From Store_Fact Where Security Filter
The string Where Security Filter would be replaced by Where Store_ID = 1 when the report is executed for a user who has a security filter (Store@ID = 1) like the following:Select Year_ID, Store_ID, M1 From Store_Fact Where Store_ID = 1
Parameters for security filters
The following parameters need to be specified when you create security filters in the Freeform SQL Security Filter Editor:
To complete the string, add “where” or “and” in front of “Security Filter”. If there is no valid security filter, then the whole string (“where Security Filter” or “and Security Filter”) does not appear in the generated report SQL. For example, following the example mentioned above, when a user without a security filter runs the same report, the SQL looks like the following:Select Year_ID, Store_ID, M1 From Store_Fact
As you can see, the whole security filter string is dropped from the generated SQL statement.
If you write “where” or “and” directly into the SQL statement in the Freeform SQL Editor, instead of in the ReplacementString field in the Freeform SQL Security Filter Editor, the following will happen:
Only Year = 1998 is applied when the report is generated.
Exercise caution with this option:
Creating a security filter
Security filters are created in the Freeform SQL Security Filter Editor, which can be accessed by selecting Insert Security Filter option from the Edit menu in the Freeform SQL Editor. For step-by-step instructions, please refer to the online help (search for “Creating security filters for Freeform SQL reports”).
When you close the editor, the security filter string is automatically inserted into the SQL statement at the current cursor location. The string is displayed in an uneditable mode, just like a prompt, and is bold and underlined in green, for example, Where Store ID = 1.
You can edit the security filter after it is inserted into the SQL statement by double- clicking it or right-clicking it and selecting Edit.
Microstrategy Related Interview Questions
|Informatica Interview Questions||IBM Cognos Interview Questions|
|Teradata Interview Questions||Adv Java Interview Questions|
|Cloud Computing Interview Questions||SQL Database Interview Questions|
|OBIEE Interview Questions||Qlik View Interview Questions|
|Tableau Interview Questions||Talend Interview Questions|
|IBM Cognos TM1 Interview Questions||Data modeling Interview Questions|
|Cognos ReportNet (CRN) Interview Questions||Qlik Sense Interview Questions|
Introduction To Advanced Reporting
Creating Freeform Sql Reports
Creating Olap Cube Reports
Data Mining Services
Custom Groups And Consolidations
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.