WSE 2.0 Security token could not be authenticated or authorized -x

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Adam Zebrowski - 17 Nov 2005 15:51 GMT

Hi,

I've got strange problem. I'm using WSE 2.0. The message is signed and sent
to WSE enabled web service which should authenticate or not the message based
on policy. The WS invokes after the WSE BTS adapter. Between sender and
receiver i've got the SSL blade. So communication to ssl blade is SSL after
HTTP. The problem i'm getting is that the message is processed properly but
the above error is returned.

Any clues???

Thanks

Thanks

Reply to this Message

Pablo Cibraro - 19 Nov 2005 22:42 GMT

Hi Adam,
What kind of client token are you using ?. (UsernameToken,
X509SecurityToken, ??).
WSE is trying to authenticate that token using a Token Manager but that
process is failing for some reason.
For example, the default Username Token Manager authenticates a client token
against a valid windows domain account.

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

> Hi,
>
[quoted text clipped - 14 lines]
>
> Thanks

Reply to this Message

Adam Zebrowski - 21 Nov 2005 18:24 GMT

Hi Pablo,

I've put in the subject that it's x509, but i guess the was truncated and
you can see only "x".
Anyway the strange thing is that despite authentication failure the message
is processed correctly.

Thanks,

Adam

> Hi,
>
[quoted text clipped - 10 lines]
>
> Thanks

Reply to this Message

WSE 2.0 Security token could not be authenticated or authorized -x

Free Magazines