Deploying with custom Forms Security enabled

I have recently enabled a custom Forms Security on my Windows 2003 Server w/ SQL Server 2005 Reporting Services. All the functionality I would expect is working properly, except for the ability to deploy to the reports server from inside my Visual Studio 2005 Reports Project.

The 'Reporting Services Login' window opens, prompting me for a username and password. Regardless of what is supplied, the window keeps reappearing, and I am unable to deploy. I am able to upload the files from within the Report Manager, but that is time consuming and inelegant.

Any help would be greatly appreciated!

Anyone? This is pretty peculiar, and it looks like there was a similar issue with SQL Server 2000 and its reporting services. Has any experienced anything like this?|||

I too am stuck:

I have setup Forms Authentication on RS2005 and the report manager is working
swell it redirects to a log in page, authenticates against our data
source/ldap server and returns to the report manager with the appropriate
roles/authorizations.
However, I don't know how to deploy the reports/models to the report server. I no longer have a prompt in Visual Studio after we enabled the
forms authenticaiton; keeping in mind with forms authentication you aren't
using windows authorization/active directory. How do I continue to deploy
reports or report models to the report server/manager with forms
authentication. Specific configuration steps would be helpful. Currently we
get an error something to the effect that user '' doesn't have permissions to
the destination. So basically without a prompt window it doesn't seem to know
who I am anymore. How would I login or use/create a cookie to tell it who I
am if I don't have a login prompt inside the Visual Studio 2005?
Thanks!

|||no idea. it doesnt make sense that the prompt in visual studio would disapper, however, since the reports could be deployed to any server...|||I had the same problem: I was prompted for username/password in my Report Model and Report Server projects. Deploying the Report Server project worked fine, but the Report Model project sent an empty username string to the logon function.

I finally figured out that the two project types handle the username string differently. For getting the Report Model to deploy correctly, you must specify an authority before the username even if you don't use one in your custom security extension. (i.e. ANYTHING\username or .\username, \username doesn't work). Done so, the username string gets parsed correctly and the deployment works fine.
|||bump.... I'm not even getting a dialog...

|||

Not sure if anyone out there is still struggling with the continual login dialog or not. I was and found out what my problem was. I was trying to deploy to "http:\localhost\reports" instead of http:\localhost\ReportServer"!

ugh!

Anyway, hope this helps someone!