I recently had the great pleasure of solving a PerformancePoint 2013 puzzle and I thought I’d share how I did it to help others and as a reference for my fellow colleagues. Our team was trying to implement dynamic active directory security for PerformancePoint 2013 dashboards. A variety of PerformancePoint web parts were tested as part of this endeavor including Analysis Services scorecards, analytic charts and grids, SSRS reports (native mode), and Excel Services.
Devin Knight does an excellent job of explaining how to get this to work in his blogpost: Analysis Services Dynamic Security.
For this method to work with PerformancePoint and Excel Services we will need two Roles: ReadUserName and ReadCustomData. The first one, ReadUserName is set up exactly how Devin describes. This will be the role that Excel and SSRS will use. The second one, ReadCustomData is the same except you need to replace the function UserName() with CustomData(). This ReadCustomData role will be the role that is referenced in the data source editor of PerformancePoint dashboard designer.
To test this I had to make sure that I wasn’t in any other AD groups or roles. I only had to add myself to the ReadUserName role. I did not have to be in the ReadCustomData role, only the service account that runs the SharePoint 2013 PerformancePoint content (a.k.a. Proxy.) We also have a ReadUnrestricted Role. I had to make sure I wasn’t in that role.
Here is another link, that describes how to get this working with PerformancePoint 2010: How to configure dynamic security in Analysis Services and Performance Point 2010 without Kerberos.
Here is a link that describes various methods for testing if the security is working correctly:
The series of posts below are wonderful! I won’t repeat what is said there; but, I will say I was relieved to see that this person also came to the conclusion that two roles would be needed.
Here is where things got interesting… No, really.
This post: Using EffectiveUserName To Impersonate in SSAS mentions that you have to set up Kerberos on your SSAS server to get this to work. I can tell you we got it to work without that. I did set up the data source in SSRS as this person describes. Credentials stored securely in the report server, use as windows credentials, Impersonate the authenticated user after a connection has been made to the data source.
I got a little lucky (ok, maybe a lot lucky) in that my account had certain permissions that no one else in my active directory group had. If it weren’t for that, I don’t know if I would have ever gotten any of this working.
Our initial goal was to set these permissions on either the SharePoint proxy account or the domain service account that process the cube. That worked for the SSRS MDX reports; but, the Excel Services dashboard pages quit working. Currently we are faced with the possibility that these permissions will need to be set for all the dashboard users and we are investigating what that actually means. (http://windowsitpro.com/active-directory/hiding-data-active-directory-part-3-enabling-list-object-mode-forest)
We think the List contents is the one that made the difference. My Active Directory sent me these links that he felt describe what is going on pretty well. Here is what he said:
‘The link below explains the end result as the Account authenticating for the SSRS reports needs Read access to the TokenGroupGlobalAndUniversal attribute. This is done by adding the required account to the Windows Authorization Access group in Active Directory.
Originally it was thought the SharePointProxy account was the account being used. I did add it to the group last Saturday and it did not resolve the issue. But today it was identified that the service account that connects to the data warehouse for cube processing was the account needing to verify the users group memberships to present the reports based on this information to the clients.
I also confirmed this to be the attribute by allowing Read access to all the User Object attributes and removing them until this single attribute was remaining. Removing this last attribute denied the reports with the Unknown username or password error.’
The other piece that seemed to make a difference was that the SSAS service is running under the NT AUTHORITY\NetworkService account.
Post in the comments if you have questions.