WSE 2.0 - Multiple Web Services in the Same Project

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jon_ProactiveLogic - 10 Jan 2006 22:09 GMT

Hi,
I have an existing ASP.NET 1.1 web service project that has a web service
secured by WSE 2.0. Adding a second .asmx page to the project with new web
methods, are not secured. They both share the same Web.Config file, so how
can this be?

Thanks,
Jon

Reply to this Message

Pablo Cibraro - 11 Jan 2006 13:29 GMT

Hi Jon,
That happens because your policy applies to an specific endpoint (The first
asmx).
You should modify the policy file to add the new endpoint or use the default
endpoint. Take a look to the mapping section in the policy file.
For example, this policy uses the default endpoint, which applies to any
endpoint in the virtual directory.

<mappings xmlns:wse="http://schemas.microsoft.com/wse/2003/06/Policy">
<defaultEndpoint>
<operation requestAction="GetProductInformation">
<request policy="#x509-request" />
<response policy="" />
<fault policy="" />
</operation>
</defaultEndpoint>
</mappings>

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com

> Hi,
> I have an existing ASP.NET 1.1 web service project that has a web service
[quoted text clipped - 6 lines]
> Thanks,
> Jon

Reply to this Message

Jon_ProactiveLogic - 11 Jan 2006 16:51 GMT

Hi Pablo,

Thanks for your response! I'm actually much more familiar with WSE 3.0 than
WSE 2.0 in regards to policy. I see how WSE 2.0 policy can tie to specific
end points, but my current customer has a web service that was secured with
WSE 2.0 for some time without a policy file at all. (for many months before
I was here). They just had a custom UserNameTokenManager and settings in the
Web.config file to load the WSE soap extension and custom
usernametokenmanager setting.

Why would the first service have loaded the UserNameTokenManager with no
policy file? The second one does not. I'm fine with configuring policy, but
would really like to know the reason the first service loaded the
UserNameTokenManager without a policy file.

Thanks for any insights.
Jon

> Hi Jon,
> That happens because your policy applies to an specific endpoint (The first
[quoted text clipped - 29 lines]
> > Thanks,
> > Jon

Reply to this Message

Pablo Cibraro - 11 Jan 2006 18:25 GMT

Hi Jon,
Probably, the first service is specifing the credentials by means of code
instead of policy file.
The UsernameTokenManager is loaded only when the service receives
a message with a UsernameToken as client token.
I will be better if you turn on the WSE trace and see the messages for both
services. (You will notice the difference there).

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com

> Hi Pablo,
>
[quoted text clipped - 56 lines]
>> > Thanks,
>> > Jon

Reply to this Message

WSE 2.0 - Multiple Web Services in the Same Project

Free Magazines