Welcome to PerformancePoint Insider Sign in | Join | Help
One Hop, Two Hop, Three Hop and you are screwed...

Big Smile  So when you are building your PerformancePoint Server solutions, if you have everything on one machine it works great, but when you setup seperate machines, security always becomes kind of a pain.  You need to setup Kerberos to setup trust between the web and database servers if you want the users credentials to pass over to the data sources.

If you do not need that and can live with a hard coded credential, you can use a custom data connection string to impersonate a user.   Only one user.   I used the following web site to create my string.

http://www.ssas-info.com/ssas_articles/ssas_articles/analysis_services_2000_and_2005_connection_string_properties.html

or here is a string to use

Provider=msolap.3;Datasource=olapservername;Initial Catalog=olapdatabasename;User ID=domain\alias;Password=password;Impersonation Level=Impersonate;

Posted: Wednesday, October 31, 2007 6:42 AM by Patrick Husting

Comments

dgosbell said:

I think you will find that the User ID/Password paramenters are being ignored as they are only supported for http authentication. You will most likely find that it is the identity of your web application that is being used by PPS M&A to connect to SSAS.

# November 25, 2007 3:45 PM
Anonymous comments are disabled