Rampart
  1. Rampart
  2. RAMPART-334

Unable to set TTL and maxTimeStampSkew values through a rampart callback

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: 1.6.2, 1.7.0
    • Component/s: rampart-core
    • Labels:
      None
    • Environment:
      Ubuntu

      Description

      Even though we set timestamp TTL and max timestamp skew values through configuration or configuration callback, updated values are not read during actual message processing.

      To reproduce the issue follow steps given below,
      1. Write a rampart configuration callback
      2. Write a validation callback
      3. Print TTL and maxTimestampSkew values in the validator

      Updated values should be printed. But as per now only default values are printing.
      Attaching a service code which can be used to reproduce this issue.

      1. service.zip
        28 kB
        Amila Jayasekara
      2. rampart-334.diff
        1 kB
        Amila Jayasekara

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Thilina Buddhika
            Reporter:
            Amila Jayasekara
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development