Our developers have developed webservices using Apache CFX. The problem I
have is that the application I am using can not construct the timestamp part
for the security header. Is there a simple configuration change that I can
make on the application side to ignore the timestamp. Below is an example of
the header my webservices is expecting. I need to call it with timestamp
removed.

If there is a better list to post these types of questions - please let know
that as well.


<soapenv:Header>
      <wsse:Security soapenv:mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsu:Timestamp wsu:Id="Timestamp-20874988"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsu:Created>2009-05-20T20:50:03.317Z</wsu:Created>
            <wsu:Expires>2009-05-21T13:30:03.317Z</wsu:Expires>
         </wsu:Timestamp>         <wsse:UsernameToken
wsu:Id="UsernameToken-30892496"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:Username>PortalAdmin</wsse:Username>
            <wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PortalAdmin</wsse:Password>
         </wsse:UsernameToken>
      </wsse:Security>
</soapenv:Header>

--
View this message in context: http://www.nabble.com/CFX-Header-Security-Configurations-tp25196332p25196332.html
Sent from the Axis - Dev mailing list archive at Nabble.com.