Connection Maps: Standard Authentication, Connection Maps, and Partitioned Fact Tables

You may want to use this configuration if you implement access control policies in the RDBMS so that you can have multiple user accounts in the RDBMS, but not necessarily one for every user. In addition, you must use connection maps to enable report subscriptions if you are using Microsoft Analysis Services with integrated authentication.

For example, you are partitioning fact tables by rows, as described in Controlling Access to Data at the Database (RDBMS) Level. You have a user ID for the 1st National Bank that only has access to the table containing records for that bank and another user ID for the Eastern Credit Bank that only has access to its corresponding table. Depending on the user ID used to log in to the RDBMS, a different table is used in SQL queries.

Although there are only a small number of user IDs in the RDBMS, there are many more users who access the MicroStrategy application. When users access the MicroStrategy system, they log in using their MicroStrategy user names and passwords. Using connection maps, Intelligence Server uses different database accounts to execute queries, depending on the user who submitted the report.

To Establish this Configuration

1. In Developer, open the Project Source Manager and click Modify.
2. On the Advanced tab, select Use login ID and password entered by the user (standard authentication) as the Authentication mode. This is the default setting.
3. From Web, log in as an administrator and select Preferences, select Project Defaults, select Security, and then enable Standard (user name & password) as the login mode.
4. Create a database login for each of the RDBMS accounts.
5. Create a user group in the MicroStrategy system corresponding to each of the RDBMS accounts and then assign multiple users to these groups as necessary.
6. Define a connection mapping that maps each user group to the appropriate database login.