Hello - I have the following setup but the dynamic security does not
seem to be working.

2 Base cubes:

a) Security cube

Employee dimension

Accounts dimension

b) Sales cube

Accounts dimension
10 other dimensions



1 Virtual Cube that combines the above cube



2 Roles are applied to the Virtual Cube:


Role I: ROLE_ALL – has company\user1 as the user

Role II: ACCOUNT_ROLE – has company\user2 as the user



ACCOUNT_ROLE has dimension level restriction.. Below is the
statement:



filter([DM_Account].[AccountId].members,
validmeasure(([securityflag],[DM_Account].currentmember,

strtomember("[DM_Employee].[Emp Id].[" +
mid(username,instr(1,username,"\")+1,len(username) ) + "]"))) = 1)





PROBLEM:



From Panorama if I try and log in as company\user2, it gives me all
accounts when it should only give me 10 accounts. This works with in
the MDX sample application. It seems to be that this is an OLAP issue
and not a client software issue. THis is applied to the role at the
cube level.

Thank you for your helP!

Nikhil

If this works in MDX Sample, but doesn't work in Panorama, I am inclined to
think that the problem is in how Panorama does impersonation.

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

One way to check this would be by creating a simple calculated member
with a single function "USERNAME" in the cube.

Try logging into Panorama with some userid and browse that username
calculated member.

If it returns the proper USENAME then the impersonation is happening
well... if not then obviously - panorama is not passing the user's
credentials all the way to OLAP - meaning dynamic security cannot be
applied using USERNAME function.

Give this a try. It could be helpful.

Thanks