You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Narayan S Dhillon (JIRA)" <ji...@apache.org> on 2008/03/04 12:16:40 UTC

[jira] Commented: (RAMPART-144) Timestamp with just create time element

    [ https://issues.apache.org/jira/browse/RAMPART-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574936#action_12574936 ] 

Narayan S Dhillon commented on RAMPART-144:
-------------------------------------------

So the usecases I could see now are - 
(1) Timestamp with created and expires time including both are equal.
(2) Timestamp with just created time

That means we would need to use another configuration parameter - 
timestampExcludeExpiryTime, if that element is present then it means expiry time wont be created.


> Timestamp with just create time element
> ---------------------------------------
>
>                 Key: RAMPART-144
>                 URL: https://issues.apache.org/jira/browse/RAMPART-144
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.3
>            Reporter: Narayan Singh Dhillon
>            Assignee: Ruchith Udayanga Fernando
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> If we want to just have "wsu:Created" element inside "wsu:Timestamp" then Rampart doesn't allow it. 
> WS-Security policy doesn't seem to define any policy semantics for above, but this element is optional and often not used in practical scenarios because of clock differences, but it is considered best practice to have time stamp included in XMLdSig.
> I think as Created and Expires elements are not controlled by WS-Policy, we could adopt for the flexible solutions as below:
> (1) In client side, if timestampTTL element in rampart-config is set to 0, then wsu:expires element must not be created.
> (2) On Server side, Timestamp should be validated for full, that is if Created and Expires element are present then they should be validated otherwise just created time be validated. I think this is current behaviour.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.