Groups | Blog | Home
all groups > dotnet web services enhancements > october 2006 >

dotnet web services enhancements : throwing soap exception from wse? / token manager


mike wolf
10/23/2006 6:41:02 AM
Hey everyone, im trying to throw a valid soapexception from a wse service w/
a custom token manager, when ever I throw any exception I get this on the
client "Security requirements are not satisfied because the security header
is not present in the incoming message"

mike wolf
10/23/2006 7:53:01 AM
so in short, if your using a custom token manager there is no real supported
or recomended way for returning a custom exception. Any idea if this is by
design some how? Seems silly.

[quoted text, click to view]
Pablo Cibraro [MVP]
10/23/2006 10:08:20 AM
Hi Mike,

WSE always returns the "Security requeriments ..." message when an exception
is thrown in a custom token manager (The real exception message is also
attached to the SoapException). There is no way to change that behavior, but
some people have worked on some workarounds or dirty hacks to solve that
problem. For instance, throwing the exception from the web service or a
custom assertion. Anyway, it is not something I recommend.

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

[quoted text, click to view]

Pablo Cibraro [MVP]
10/23/2006 2:56:29 PM
Yes, it is by design. You can throw an exception from a custom token
manager, but the client application will always receive a soap exception
with the message "Security Requeriments...." + original message. (You can
have some code in the client to parse that message).

Regards,
Pablo.


[quoted text, click to view]

AddThis Social Bookmark Button