sql server reporting services:
Chris,
I didn't have the chance to integrate Forms Authentication with WinForm
applications but it all boils down to passing the sqlAuthCookie cookie back
to the Report Server. So, basically your client needs to store the cookie
received from the response and pass it back with the new request. You can
use tcpTrace to capture the SOAP traffic to find out if the cookie is
present.
Perhaps, the RS team can share some code with us.
--
Hope this helps.
----------------------------------------------
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com [quoted text, click to view] "Chris Lewis" <chris.lewis@xntra.co.uk> wrote in message
news:OetcovUgEHA.904@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> We have a RS ReportServer webservice that is called from an ASP.NET web
app,
> which uses Forms authentication through a custom authentication extension.
> We also have a webservice client that runs within a Windows service that
> needs to make calls to (i.e. consume) the same RS webservice.
>
> You will have to forgive the laymans language here, but Http, cookies,
SOAP,
> etc are not my strong points. We are using the 'extended' webservice proxy
> that was included with the Forms authentication custom component example
on
> MSDN; this proxy does all the management of Http cookies. This all works
> well for the web app. However, our problem is that the Windows service
> client is obviously not running in an HttpContext, and the proxy does not
> work (as the necessary HttpContext does not exist).
>
> I have tried settings credentials on the proxy, but to no avail - Forms
> authentication doesn't recognise then and redirects to the login page!
>
> Please help - I don't know where to start with this.
>
> Thanks, in anticipation.
>
> Chris
>
>
