Martin, WSS4J provided a specific parameter (timeToLive) to set a timestamp values to any (meanningfull) value you choose, plase have a look at WSS4J FAQ in the WSS4J Wiki, there is fairly comprehensive discussion about this topic.
On the other hand that's a somewhat difficult issue because if you cannot predict the latency to delivery the message. Does MQ store the messages and deliver it only after a lengthly period of time? What do you mean in this respect with "asynchronous"? Ist it an asynchronous message exchange pattern (MEP)? Regards, Werner > -----Ursprüngliche Nachricht----- > Von: Martin Stemplinger [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 15. Dezember 2005 10:09 > An: [email protected] > Betreff: timestamps in wss4j and asynchronous messaging > > Hi all, > > I use the WSDoAllReceiver as an axis handler for processing > UsernameToken. This works great using http. But now I need to use MQ > Series and thus can't guarantee that the message arrive within 5 > minutes. But then the timestamp processing fails. While this is > correct per the WSS spec and the basic security profile, it does not > make sense in this scenario. I tried to understand the spec but didn't > succeed :-(. > > I'd appreciate any hints how the spec supposes to handle asynchronous > requests. The only solution so far seems to be to switch off timestamp > handling which I'd rather do not because I'd like to retain the > anti-replay feature. > > Thanks in Advance! > > Martin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
