Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > No SoapContext

Reply
Thread Tools

No SoapContext

 
 
APA
Guest
Posts: n/a
 
      01-17-2007
In the constructor of my web service I have no access to the SoapContext (i.e. RequestSoapContext.Current). Not only that but I have implemented a
customer UsernameTokenmanger.AuthenticateToken method and it doesn't call that either. I have the following setup in my web.config

<configSections>
<section name="microsoft.web.services3" type="Microsoft.Web.Services3.Configuration.WebSer vicesConfiguration, Microsoft.Web.Services3,
Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</configSections>

and

<microsoft.web.services3>
<security>
<securityTokenManager type="AppCommonProj.CustomUsernameTokenManager, AppCommonProj"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" qname="wsse:UsernameToken"/>
</security>
<diagnostics/>
</microsoft.web.services3>




I'm using a testing tool (that works fine with other web services that I've developed in .NET 1.1 but this web service is developed in .NET2.0 using
WSE3. I'm not really doing anything odd just checking the SoapContext to see if the request was made using SOAP and not using POST or GET. Here's
what I'm doing in my web service's constructor.


SoapContext sContext = RequestSoapContext.Current;
if (sContext == null)
{
throw new Exception("Invalid web service request.");
}



sContext is always null. Have no idea why and I don't understand why the UsernameTokenmanger.AuthenticateToken method is not being called either.



TIA.
 
Reply With Quote
 
 
 
 
APA
Guest
Posts: n/a
 
      01-17-2007
Well I got by this problem when I went through the WSE3 setup wizard and then deleted all the policy crap that it created. However, my custom
AuthenticateToken method is still not called. The WSE3 setup wizard modifed the securityTokenManager element to look like this but it still never
calls it (and never tried even with the policy stuff).


<microsoft.web.services3>
<security>
<securityTokenManager>
<add type="AppCommonProj.ASPDNSFUsernameTokenManager, AppCommonProj"
namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" localName="UsernameToken" />
</securityTokenManager>
</security>
<diagnostics />
</microsoft.web.services3>



What took me 10 minutes in WSE2 is taking 6 hours in WSE3 what a POS.
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
WSE 1.0, InputFilter, SoapContext oliver.wulff@zurich.ch ASP .Net Web Services 0 02-01-2004 09:40 PM
Simple WSE 2.0 question: passing data thru SoapContext Jerry ASP .Net Web Services 2 08-01-2003 03:56 PM



Advertisments