[
https://issues.apache.org/jira/browse/AXIS2C-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485429
]
Malinda Kaushalye Kapuruge commented on AXIS2C-263:
---------------------------------------------------
For the replay detection I have this idea to give user an interface.
The interface has following methods.
status = Load(env, rd_module);
status = Is_Replayed(env, rd_module, msg_ctx);
status = Close(env, rd_module);
Note: Rd_module is the replay detection module.
Summary:-
Load(): Loads the data source, which can be a database, flat file etc.
Is_Replayed() : Check if the current message is replayed with the existing
records.
Close(): Free resources allocated. Close data connections etc.
In this way the user can have his own logic to check whether the message is
replayed or not. He may use the wsa:Message-ID, Timestamps, Nonce or even the
digest of the message. User can configure the time frame or the message count
frame for the replay detection.
We have to implement a sample replay detection module based to set an example
for Rampart/C users.
Thoughts please.
Cheers,
Kau
> Replay detection needed
> -----------------------
>
> Key: AXIS2C-263
> URL: https://issues.apache.org/jira/browse/AXIS2C-263
> Project: Axis2-C
> Issue Type: Bug
> Components: rampart
> Affects Versions: Current (Nightly)
> Reporter: James Clark
> Assigned To: Malinda Kaushalye Kapuruge
> Priority: Critical
>
> You need to implement replay detection. See section 13.2.1 of WS-Security
> 2004.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
