![]() | ![]() | ![]() | ![]() |
BI row-level permissions enable you to limit access to SAS data and third-party relational data that is accessed through information maps. Row-level permissions are enforced when information maps are accessed from applications such as SAS® Web Report Studio.
This sample shows you how to create a simple identity-driven, row-level permission in SAS Information Map Studio. As the input table for the information map, this sample uses the SASHELP.CLASS table.
Note: Row-level permission filters also can be based on group membership (see Sample 31885).
Tip: If your environment includes a SAS Demo User, then use that account to follow along with the sample steps.
A security associations table documents the relationships between a user and the information that you want to control access to. The following DATA step code was used to create the security associations table that is used in this sample.
data sashelp.rlp_class;
input PersonName $13. @14 Gender $;
datalines;
SAS Demo User F
SAS Guest M
;
run;
|
Note: Remember to register the security associations table in SAS® Management Console.
In this sample, SAS Demo User is given permission to only view information for females and SAS Guest is given permission to only view information for males.
| About the security associations table
Instead of creating a separate security associations table, the PersonName column could have been added to the CLASS table. In this case, SAS Demo User would have been the value in the female rows and SAS Guest would have been the value in the male rows. |
Sex in the CLASS table with Gender in the RLP_CLASS table.
PersonName column, and then click Add to Expression.
From the drop-down list beneath Value(s), select Derive identity values (for row-level permissions) to see a list of identity-driven properties. This sample filters on SAS.PersonName.

Expand Filter expression at the bottom of the dialog box to see the criteria that you have just defined.
|
About the Example column
The examples are derived from the currently logged in user (in this sample, the user is SAS Demo User). The examples are showing you how the value for the identity property should appear in the security associations table. This sample filters on SAS.PersonName. The sample could also filter on the SAS.IdentityName property. If the security associations table had included the values SASDEMO@d20093 and SASGUEST@d20093, then the sample could have filtered on the SAS.Userid property. |
|
About prefilters
A prefilter is a mandatory filter that pre-screens and subsets the data in its associated table before any other part of a query is run. |
To see results of testing this filter in SAS Information Studio and SAS Web Report Studio, click the Results tab at the top of this sample.
For more information about creating row-level permissions, see "Chapter 10: BI Row-Level Permissions" in the SAS 9.1.3 Intelligence Platform: Security Administration Guide at http://support.sas.com/documentation/configuration/bisecag.pdf
For a list of available documentation for SAS Information Map Studio, see http://support.sas.com/documentation/onlinedoc/ims/index.html
For a list of available documentation for SAS Web Report Studio, see http://support.sas.com/documentation/onlinedoc/wrs/index.html.
For a list of available documentation for SAS Management Console, see http://support.sas.com/documentation/onlinedoc/sasmc/index.html.
These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.
These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.

| Type: | Sample |
| Topic: | Query and Reporting ==> Interactive Querying Query and Reporting System Administration ==> Security ==> Authentication System Administration ==> Security ==> Permissions Data Management ==> Data Sources ==> Information map |
| Date Modified: | 2008-03-24 16:54:37 |
| Date Created: | 2008-03-22 18:03:58 |
| Product Family | Product | Host | Starting Release | Ending Release |
| SAS System | SAS Information Map Studio | Microsoft® Windows® for x64 | 3.1 | |
| Microsoft Windows 2000 Advanced Server | 3.1 | |||
| Microsoft Windows 2000 Datacenter Server | 3.1 | |||
| Microsoft Windows 2000 Server | 3.1 | |||
| Microsoft Windows 2000 Professional | 3.1 | |||
| Microsoft Windows NT Workstation | 3.1 | |||
| Microsoft Windows Server 2003 Datacenter Edition | 3.1 | |||
| Microsoft Windows Server 2003 Enterprise Edition | 3.1 | |||
| Microsoft Windows Server 2003 Standard Edition | 3.1 | |||
| Microsoft Windows XP Professional | 3.1 | |||
| SAS System | SAS Web Report Studio | Microsoft® Windows® for x64 | 3.1 | |
| Microsoft Windows 2000 Advanced Server | 3.1 | |||
| Microsoft Windows 2000 Datacenter Server | 3.1 | |||
| Microsoft Windows 2000 Server | 3.1 | |||
| Microsoft Windows 2000 Professional | 3.1 | |||
| Microsoft Windows NT Workstation | 3.1 | |||
| Microsoft Windows Server 2003 Datacenter Edition | 3.1 | |||
| Microsoft Windows Server 2003 Enterprise Edition | 3.1 | |||
| Microsoft Windows Server 2003 Standard Edition | 3.1 | |||
| Microsoft Windows XP Professional | 3.1 | |||
| 64-bit Enabled AIX | 3.1 | |||
| 64-bit Enabled Solaris | 3.1 | |||
| HP-UX IPF | 3.1 |




