StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POclientaccesspolicy.xml suddenly stopped working (WCF/Silverlight)
text
Body
copied!<p>Very frustrated with all of this, hoping someone can assist.</p> <p>I had a Silverlight application and WCF working together without issue for a year. In order to get them working, I had some pain initially but finally worked through it with help. All of the pain came from configuration/security, 401's, cross-domain hell, etc.</p> <p>The way I have everything setup is that I have a WCF service that resides in it's own application/directory and runs in its own application pool.</p> <p>On the same web server (IIS7), I have another application/directory with the Silverlight application that points to the aforementioned service.</p> <p>The server name (for this exercise) is WEBSERVER1. We've created a CNAME for it that is WEB1. In the past, if the user went to <a href="http://WEB1/MyApp/" rel="nofollow">http://WEB1/MyApp/</a> or <a href="http://WEBSERVER1/MyApp/" rel="nofollow">http://WEBSERVER1/MyApp/</a> it would work. Suddenly yesterday it started behaving badly. Normal users started getting the Windows challenge/response prompt (and even if they entered the info they would get a 401 error).</p> <p>My WCF service runs in a site that enables anonymous access (and this has always worked). My Silverlight application runs in a site that has windows integrated (and this has always worked), since I capture the Windows username when they connect.</p> <p>For the record, I did create a NEW application pool yesterday with an ASP.NET application that runs in it. This seems to work fine, but there is a chance creating this new application pool and application/directory has caused something to change.</p> <p>I have a clientaccesspolicy.xml in my wwwroot folder, as well as in the folder for each of the two applications above (just in case). I have tried to promote NTLM over Negotiate as a provider (as that worked for another issue I was having on another server).</p> <p>After trying some changes, I can't even get the thing to behave the same each time I call it. Sometimes it will prompt me for credentials. Other times it will work, but then say it failed to connect with the WCF service with a "not found". Other times it will actually work fine, but only if I am using the actual server name and not the CNAME. When using the CNAME I always get the crossdomain error, even though I have the cross-domain xml files in every directory root.</p> <p>This is a nightmare, and makes advanced algorithm analysis seem fun and easy by comparison. Did Microsoft realize how difficult they made this combination of (IIS7/WCF/Silverlight/providers/permissions/cryptic or missing error messages) to get to work??</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload