J
James
In an Extranet configuration, we want to give access to shop managers
worldwide to an Analysis Services database through OWC.
We cannot use Windows authentication, and each shop manager should only see
data corresponding to his shop.
AS only supports Windows authentication.
What I'm trying to do is use OLAP role-based security to ensure that the
Denver shop manager only gets Denver data delivered into his OWC pivot table.
I have tried Forms Authentication, and read the following article, that
supposedly makes recommendations for my kind of scenario
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp
(the article uses SQL Server instead of AS)
The problem is, using this recommendation, all users come to the database as
ASPNET. I cannot differenciate at the database level between the Denver shop
manager and the Vancouver shop manager.
Can anybody think of a solution for this type of organisation? I would think
that this scenario would be pretty common.
I have gotten so far as to note that the
HttpContext.Current.User.Identity.Name does contain the name of the logged-in
user, but the System.Security.Principal.WindowsIdentity.GetCurrent().Name
still contains ASPNET. And that's the one that AS is using for
authentication. Is there a way I can force the WindowsIdentity to be the same
as HttpContext ?
worldwide to an Analysis Services database through OWC.
We cannot use Windows authentication, and each shop manager should only see
data corresponding to his shop.
AS only supports Windows authentication.
What I'm trying to do is use OLAP role-based security to ensure that the
Denver shop manager only gets Denver data delivered into his OWC pivot table.
I have tried Forms Authentication, and read the following article, that
supposedly makes recommendations for my kind of scenario
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp
(the article uses SQL Server instead of AS)
The problem is, using this recommendation, all users come to the database as
ASPNET. I cannot differenciate at the database level between the Denver shop
manager and the Vancouver shop manager.
Can anybody think of a solution for this type of organisation? I would think
that this scenario would be pretty common.
I have gotten so far as to note that the
HttpContext.Current.User.Identity.Name does contain the name of the logged-in
user, but the System.Security.Principal.WindowsIdentity.GetCurrent().Name
still contains ASPNET. And that's the one that AS is using for
authentication. Is there a way I can force the WindowsIdentity to be the same
as HttpContext ?