Yes, it is by design. You can throw an exception from a custom token
with the message "Security Requeriments...." + original message. (You can
"mike wolf" <mikewolf@discussions.microsoft.com> wrote in message
news:178BBC02-D204-4B49-B1CB-20182224FB6B@microsoft.com...
> 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.
>
> "Pablo Cibraro [MVP]" wrote:
>
>> 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 >>
>> "mike wolf" <mikewolf@discussions.microsoft.com> wrote in message
>> news:824936AE-860E-452E-BEFF-B493F75EB4EB@microsoft.com...
>> > 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?
>>
>>
>>