Mixing and matching security to get something like this locked down and providing the desired exposure might be challenging but I didn't offer to solve that in the title, did I?
<system.serviceModel>
<behaviors>
<endpointBehaviors>
<behavior name="webScriptBehavior">
<enableWebScript />
</behavior>
</endpointBehaviors>
<serviceBehaviors>
<behavior name="Salient.ScriptModel.Services.DualServiceBehavior">
<serviceMetadata httpGetEnabled="true" />
<serviceDebug includeExceptionDetailInFaults="false" />
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
<services>
<service behaviorConfiguration="Salient.ScriptModel.Services.DualServiceBehavior" name="Salient.ScriptModel.Services.DualService">
<endpoint address="" binding="wsHttpBinding" contract="Salient.ScriptModel.Services.IDualService"/>
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
<endpoint address="json" behaviorConfiguration="webScriptBehavior" binding="webHttpBinding" contract="Salient.ScriptModel.Services.IDualService"/>
</service>
</services>
</system.serviceModel>
Technorati tags:
WCF,
Ajax,
CodeProject-Tip
My name is Sky Sanders and I am an end-to-end, front-to-back software solutions architect with more than 20 years experience in IT infrastructure and software development, the last 10 years being focused primarily on the Microsoft .NET platform.
My motto is 'I solve problems.' and I am currently available for hire.
I can be contacted at sky.sanders@gmail.com
Submit an article or tip
