5 Replies Latest reply on Mar 1, 2013 10:34 AM by user9024636

    custom WS-Policy in OSB 11g - <wsu:timestamp> not first in header

      A custom WS-policy is configured on an OSB 11g Business Service for encrypting a part of the message header (UsernameToken part is being encrypted). This is working fine.

      We need to modify this WS-Policy to add Timestamp to the WS security header. We tried adding <MessageAge> assertion to the policy - this is working fine except that the timestamp element is not coming as the first element in security header - instead EncryptedKey is the first element. For example, the output is like below:


      OWSM is not an option as client do not want it yet.

      If anyone knows the solution, kindly let me know.