Forum Discussion
Analysis Services Connector limitations
Try to log in as different users and see whose credential are being passed while looking at the same report . I guess I misspoke when I said that no EffectiveUserName is passed, but credentials of the user viewing reports are not being passed.
please see this blog post for more details
To describe the behavior, if UserA creates a new Dataset and choosing an Analysis Services connection that exists, that dataset will pass UserA via EffectiveUserName. If UserB creates a new dataset and choose the same AS Connector, UserB will be passed via EffectiveUserName.
Here is what I think you are encountering.
UserA creates a Dashboard, report and dataset based on an Analysis Services connection using the AS Connector. When UserA uses the items, UserA will be passed via EffectiveUserName. When UserA shares the dashboard with UserB, and UserB goes to use the Dashboard/Report, UserA will still be passed via EffectiveUserName. This is because UserA owns the asset and is letting UserB use it.
Ideally UserB would be passed via EffectiveUserName in that scenario, but that isn't the current behavior.
That said, if UserB creates his own items based on the same AS Connector item, UserB will be passed via EffectiveUserName.
That's correct. Therefore, I would advise using caution when AS Connector-based content is shared, because this behavior is counterintuitive and could have very serious security repercussions until it's fixed for GA.
As of right now it is definitely a limitation.