views:

258

answers:

3

I'm very new to AD LDS and experienced but not qualified with SSAS, so my apologies for my ignorances with these.

We have a couple implementations where we expose SSAS via an HTTPS proxy (msmdpump.dll) and currently we have a temporary domain setup handling this (where our end-users have a second account+creds to manage because of this = non-ideal). I want to move us towards a more permanent solution which I'm thinking of moving all authentication to AD LDS for our web apps, SSAS, and others. However, SSAS is where I'm concerned about this.

I know SSAS requires Windows Authentication and to play nicely, and that this ultimately means Active Directory will be involved.

Is there a way to get this done with AD LDS instead of having to use a full AD DS implementation? If so, how?

+1  A: 

Nope, SSAS requires a full AD account for authentication.

James
Is this documented somewhere? Don't mean to be rude but I'd love it if I could have a link for me to refer to in my documentation. :-)
Jaxidian
A: 

We ended up just going with full AD-DS instead of AD-LDS.

Jaxidian
A: 

I could not find how to comment.

What does "SSAS requires a full AD account for authentication" mean???

I am BI (SSAS) developer and work with MSSQLServer Developer Ed. SSAS on Windows XP Pro isolated machine without any AD

Can I ask you to share with your experience on the reasons, difficulties why have you ended up with full AD DS?

vgv8