You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by David Bunzli <Da...@health.qld.gov.au> on 2007/06/14 05:12:23 UTC

setting timeToLive on the receiver end

I am trying to work out how to configure a timeToLive on the
inflowSecurity side.
 
My aim is to ensure that incoming messages have a particular expires
value on the request.
 
I've look around the WSS4J code and searched the web. I have concluded
that it must be possible given that WSHandler.verifyTimestamp takes a
timeToLive param, but I am stumped how I may influence this value
programmatically or whether something like <timeToLive> works in the
service.xml's inflowSecurity parameter.
 
The only option I can see is to alter the RequestData timeToLive value?
I can't imagine that is the only way.
 
Does anyone know how to do this?
 
Regards,
David


*****************************************************************
This email, including any attachments sent with it, is
confidential and for the sole use of the intended recipient(s).
This confidentiality is not waived or lost, if you receive it and
you are not the intended recipient(s), or if it is transmitted/
received in error.

Any unauthorised use, alteration, disclosure, distribution or
review of this email is strictly prohibited.  The information
contained in this email, including any attachment sent with
it, may be subject to a statutory duty of confidentiality if it
relates to health service matters.

If you are not the intended recipient(s), or if you have
received this email in error, you are asked to immediately
notify the sender by telephone collect on Australia
+61 1800 198 175 or by return email.  You should also
delete this email, and any copies, from your computer
system network and destroy any hard copies produced.

If not an intended recipient of this email, you must not copy,
distribute or take any action(s) that relies on it; any form of
disclosure, modification, distribution and/or publication of this
email is also prohibited.

Although Queensland Health takes all reasonable steps to
ensure this email does not contain malicious software,
Queensland Health does not accept responsibility for the
consequences if any person's computer inadvertently suffers
any disruption to services, loss of information, harm or is
infected with a virus, other malicious computer programme or
code that may occur as a consequence of receiving this
email.

Unless stated otherwise, this email represents only the views
of the sender and not the views of the Queensland Government.
****************************************************************