Deployed Silverlight app wont authenticate user

papa posted on Wednesday, September 30, 2009

Hi
Like some others I am using the Rolodex sample as the base for my first Silverlight project. My project runs fine on my local machine using the development Web server, however when I deploy it to IIS on a server it failes to authenticate. The method I am using to authenticate is unchanged from the Rolodex original. Currently as a test I have slugged the code so that it does not check for a valid used and commented out all of the authentication rules in my object so that I have full functionality (apart from authentication). Like I said this is my first Silverlight project - I would appreciate some guidance.
thanks

Paul

sergeyb replied on Wednesday, September 30, 2009

Chances are you need to change ServiceReference.ClientConfig inside XAP application file. You would possibly also need to put ClientAccessPolicy.xml at the root of the web site that hosts WCF service to address rights issue.



Sergey Barskiy
Principal Consultant
office: 678.405.0687 | mobile: 404.388.1899

Microsoft Worldwide Partner of the Year | Custom Development Solutions, Technical Innovation

-----Original Message-----
From: papa [mailto:cslanet@lhotka.net]
Sent: Wednesday, September 30, 2009 8:06 AM
To: Sergey Barskiy
Subject: [CSLA .NET] Deployed Silverlight app wont authenticate user

Hi
Like some others I am using the Rolodex sample as the base for my first Silverlight project. My project runs fine on my local machine using the development Web server, however when I deploy it to IIS on a server it failes to authenticate. The method I am using to authenticate is unchanged from the Rolodex original. Currently as a test I have slugged the code so that it does not check for a valid used and commented out all of the authentication rules in my object so that I have full functionality (apart from authentication). Like I said this is my first Silverlight project - I would appreciate some guidance.
thanks

Paul

papa replied on Thursday, October 01, 2009

Hi Sergey
Thanks for your help.

Moving ClientAccessPolicy.xaml was the answer. I had updated the clientConfig.

Thanks again, I would never have worked that out without your help.

Paul