Office web components basic authentication impersonation

Hi,

I have a question regarding office web components 10.0/11.0.

I've searched various forums without finding an answer.

My question is whether it's possible to use office web components with basic authentication so that the OWC uses the specified identity (basic authentication) to authenticate against AS 2000 instead of using the identity of the user that is currently logged on to the machine?

My problem is that we external users that aren't members of our AD that shall have access to AS2000. And when OWC uses the machine login instead of the basic authentication login the authentication fails.

And also, is it any difference when using OWC with AS 2000 compared to AS 2005?

I know that one solution that I've gotten to work with AS 2005 is to use HTTP connection, but then I must specify user name and password which isn't an ideal solution for us. It would be better if integrated security could be used.

Looking forward toward you answer

Regards,

Johan.

Moved as this seems to be AS related.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Not sure I get your question.

If you are trying to access Analysis Services using OWC through HTTP connection you got choice to ether use Basic Auth or Integrated. (Of cource there is anonymous)
If your user is coming from outside of AD, you got to use Basic Auth.
With Basic Auth your users needs to provide username and password, only integrated Auth works knows how to re-use existing user credentials.

HTH
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hello Edward,

My users are coming from outside of the AD. But I've created AD accounts for them to use when they login using basic authentication.

If I use HTTP connection will I have to add a username and a password in the connectionstring?

Is it possible for the user to connect to the AS database without using HTTP connection?

My experience of using OWC is that OWC will not use the identity of the web page but instead use the user's machine account.

/Johan

|||

You will need to provide usernames and passwords for Basic Auth to work.

As for protocols options to connect to Analysis Services: You have a choice of HTTP or TCP/IP.

Using TCP/IP you can establish connection to Analysis Server only using integrated windows authentication.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

> If I use HTTP connection will I have to add a username and a password in the connectionstring?

No, I think you can set up the virtual folder that holds the HTTP connectivity stuff using Basic Auth and it will then prompt and in this case you should not put the username/password in the connection string.

> My experience of using OWC is that OWC will not use the identity of the web page but instead use the user's machine account.

This is correct. OWC is an ActiveX component and it executes on the client machine (not on the server). It creates it's own connection back to the AS server. Therefore if you have Basic Auth setup on the website and on the HTTP connection, the users will get prompted twice. The only way around this would be to either:

allow anonymous access to the web page, and let the AS HTTP connection do the prompting setup an explicit username/password in the connection string, but this means you cannot apply role based security as AS only "sees" one user connecting.