Please see the thread below. In a nutshell, you need to find a way to pass
the authentication cookie to the WebBrowser control.
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=Oxge94CqEHA.868%40TK2MSFTNGP10.phx.gbl&rnum=1&prev=/groups%3Fq%3Dcookie%2Bwebbrowser%2Bgroup:*.reportingsvcs%26hl%3Den%26lr%3D%26ie%3DUTF-8%26scoring%3Dd%26selm%3DOxge94CqEHA.868%2540TK2MSFTNGP10.phx.gbl%26rnum%3D1
--
Hope this helps.
-----------------------------------------------------
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website:
http://www.manning.com/lachev Buy it from Amazon.com:
http://shrinkster.com/eq Home page and blog:
http://www.prologika.com/ -----------------------------------------------------
[quoted text, click to view] "marcca" <marcca@discussions.microsoft.com> wrote in message
news:785ECC07-D422-4F5F-8AF4-D41EBA0CB41E@microsoft.com...
> I'm doing a proof of concept on Security Extensions using the Sample
Security
> Extension. I've implemented the Sample Security Extension without any
> problems. It's worked successfully with our WinForms application, which
> manages Reporting Services using the Web Services.
>
> However, the WinForms application uses a browser control and URL Access to
> display reports to the user (We do this so the user can have the drill
down
> capabilities in the reports). Everytime a request is made using URL
Access,
> the login page is displayed. Is there a way to persist the cookie so the
> login page isn't displayed when we use URL Access?