Both the clientapplication and the webservice are written by me. I do not
want to burden my customers with handling X509 certificates. The solution is
then either to use SSL, or use the UsernameToken as encryption key, or use a
custom security token. Since SoapContext.Security becomes obsolete according
to WSE3.0 documentation, I do not know how to attach the custom security
token to the webservice communication. Are there any samples that show the
proper usage of custom security tokens for with WSE3.0 enabled webservices?

Signature
Greetings HansvL
Pablo Cibraro - 13 Jan 2006 14:07 GMT
Hi HansvL,
Writing a custom security assertion is the recommended aproach to use custom
security tokens.
You can find a good example of this in the SAML project
http://practices.gotdotnet.com/projects/saml
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
> Both the clientapplication and the webservice are written by me. I do not
> want to burden my customers with handling X509 certificates. The solution
[quoted text clipped - 7 lines]
> proper usage of custom security tokens for with WSE3.0 enabled
> webservices?