Hello all,
I use WSE 2.0 SP3 and everything works fine with the creation and
validation of UsernameTokens with WSE.
But now my architecture has been changed and this is a non-WSE client
which creates the UsernameToken. Unfortunately it's not able to produce
a nonce and a creation time in the UsernameToken.
According to the UsernameToken profile from the OASIS
(http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1
.0.pdf),
it shouldn't be a problem because they are optional.
But if I send a UsernameToken without a nonce and a creation time to a
WSE protected server, I get this error :
WSE567: The incoming Username token must contain both a nonce and a
creation time for the replay detection feature.
Does someone know how to prevent Microsoft WSE to produce an error if
no nonce or creation time is available in a UsernameToken ?
Thanks in adance,
Regards,
Mfenetre.
Naeem S. - 22 Nov 2005 15:28 GMT
I came across this same problem with a ASP web service client.
I am using a custom username token, within this class I overrided the
'DetectReplay' method. Within this function I simply did nothing. Using this
approach means you will loose the ability to detect a message that is being
repeatedly fired at the web service.
protected override void DetectReplay(UsernameToken token)
{
//do nothing
}
I hope that makes sense.
> Hello all,
>
[quoted text clipped - 21 lines]
> Regards,
> Mfenetre.
Naeem S. - 22 Nov 2005 15:29 GMT
I came across this same problem with a ASP web service client.
I am using a custom username token, within this class I overrided the
'DetectReplay' method. Within this function I simply did nothing. Using this
approach means you will loose the ability to detect a message that is being
repeatedly fired at the web service.
protected override void DetectReplay(UsernameToken token)
{
//do nothing
}
I hope that makes sense.
> Hello all,
>
[quoted text clipped - 21 lines]
> Regards,
> Mfenetre.