[RAMPART-334] Unable to set TTL and maxTimeStampSkew values through a rampart callback

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5
• Fix Version/s: 1.6.2, 1.7.0
• Component/s: rampart-core
• Environment: Ubuntu
• Assignee: Thilina Mahesh Buddhika
• Reporter: Amila Jayasekara
• Created: 19/Jul/11 17:01
• Updated: 29/Sep/11 12:19
• Resolved: 29/Sep/11 12:19

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.