Re: HTTP Access to AS 2005 not working

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I think that the issue may have to do with WinInet versus WinHttp. I believe
that MSOLAP80 used WinInet to connect to the server -- and WinInet probably
shares cookies within a process. So my guess is that if MSOLAP80 is running
inside Internet Explorer, the cookies obtained by Internet Explorer will be
automatically available to the MSOLAP80 HTTP connection.

But MSOLAP90 uses WinHttp (a similar but better and more secure API) -- I
think WinHttp does not automatically obtain the processes' WinInet cookies
and therefore you are required to re-validate.

As of now this is still just theory... I've filed a bug on this for further
investigation.

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Pat" <pat@xxxxxxxxxxxxx> wrote in message
news:8AE32C67-CF39-4EDC-9AB9-64144C198AFC@xxxxxxxxxxxxxxxx
> Hi Darren,
>
> This exact same set-up works for AS 2000, once the user is authenticated
> to
> IIS you can even open several different pages and connections without ever
> being asked for credetientials again.
>
> In any case I verified that the Default Web site doesn't have Basic auth
> enabled and that the "olap" virtual directory has basic auth enabled.


.