dotnet web services enhancements: My service requires a Username token. It also requires a
MessageSignature and EncryptedData (using said token.)

Is there any way to specify what is expected in my WSDL document? If
not, how will the service consumer know what token(s) are required?

Thanks,
-Ben
--

Hi Ben,

What u want is to specify your message requirements (which tokens are
required, etc...) in your Service Policy via WS-Policy. The good news is
WS-Policy is supported in WSE2.0.

Go to
http://msdn.microsoft.com/webservices/building/wse/default.aspx?pull=/library/en-us/dnwse/html/wse2wspolicy.asp
to find out more about WS-Policy.

hth
--
Thank you very much

Warmest Regards,
Softwaremaker
Architect | Evangelist | Consultant

+++++++++++++++++++++++++++++++++

[quoted text, click to view]

Cool. Thanks again, Softwaremaker. This looks like it's what I need.

Will the policy affect the WSDL at all? The guy coding the other side
of this (the consumer) thinks that his tool that generates code from
WSDL will handle the tokens, signature, and encryption so long as it's
specified in the WSDL. It's been frustrating working with a COM
consumer, at least so far.

[quoted text, click to view]


--

[quoted text, click to view]


[quoted text, click to view]

Hm.. I think this last idea could be a good avenue to pursue. I'll
speak with him about it.

Thanks.


--

[quoted text, click to view]

You're probably correct. However the only reason I'm going down this
road is to see if I can make integration with our existing COM toolkit
any easier. The toolkit developers can consume web services OK, but can
not figure out how to attach a Username token, sign, or encrypt the message.

Nonetheless, a policy would be a good thing to define, as it's possible
that others will be developing against this service in the long-term.

Thanks.
-Ben

--

Hi Ben,
[quoted text, click to view]

No, these are 2 different files.

[quoted text, click to view]

WSDL and Policy files are 2 different entities. WSDL specifies how your
messages should look like in terms of data and wire-formats when they reach
the endpoints. Policy files specifies whether the exchanged messages are
compatible with each other.

AFAIK, you can try to expose your Policy files thru UDDI. There is no
standard way of doing this yet, altho there is nothing to stop you from
doing it as a tModel Binding. I have not read up the specs for UDDI 3.0 yet
so I cannot comment on whether there is a standard way to do this. To help u
solve the problems your consumer may be facing, you (as the Service
Provider) may want to generate the Policy File for him and let him have it
so that his toolkit can churn out the proper message to meet your service's
requirements.

hth.
--
Thank you very much

Warmest Regards,
Softwaremaker
Architect | Evangelist | Consultant

+++++++++++++++++++++++++++++++++



[quoted text, click to view]

WS-PolicyAttachments is acutally what u shld be looking at. BUT WSE2.0
doesnt support it at this point in time so WS-PolicyAttachment is in the
Policy File itself. For now, you may want to do the below:

1) Reference policy expressions as tModels
2) Register common policy expressions as reusable tModels

hth.
--
Thank you very much

Warmest Regards,
Softwaremaker
Architect | Evangelist | Consultant
http://dotnetjunkies.com/weblog/softwaremaker

+++++++++++++++++++++++++++++++++


[quoted text, click to view]