throwing soap exception from wse? / token manager

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mike wolf - 23 Oct 2006 14:41 GMT

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"

any ideas?

Reply to this Message

Pablo Cibraro [MVP] - 23 Oct 2006 15:08 GMT

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

> Hey everyone, im trying to throw a valid soapexception from a wse service
> w/
[quoted text clipped - 4 lines]
>
> any ideas?

Reply to this Message

mike wolf - 23 Oct 2006 15:53 GMT

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.

> Hi Mike,
>
[quoted text clipped - 17 lines]
> >
> > any ideas?

Reply to this Message

Pablo Cibraro [MVP] - 23 Oct 2006 19:56 GMT

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.

> so in short, if your using a custom token manager there is no real
> supported
[quoted text clipped - 27 lines]
>> >
>> > any ideas?

Reply to this Message

throwing soap exception from wse? / token manager

Free Magazines