[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ws-general
Subject:    [jira] [Closed] (WSS-554) Improved error message for timestamp in the future
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2015-10-27 10:37:28
Message-ID: JIRA.12864082.1442277506000.70967.1445942248090 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh closed WSS-554.
-----------------------------------

> Improved error message for timestamp in the future
> --------------------------------------------------
> 
> Key: WSS-554
> URL: https://issues.apache.org/jira/browse/WSS-554
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Core
> Affects Versions: 1.6.18
> Environment: Any
> Reporter: Rudi Grasmuck
> Assignee: Colm O hEigeartaigh
> Priority: Trivial
> Fix For: 2.0.6, 2.1.4
> 
> 
> The error message "The message is expired" (WSSecurityException.MESSAGE_EXPIRED) is \
> returned for the case of  timeStamp.isExpired() as well as when the created \
> timestamp is in the future in the \
> org.apache.ws.security.validate.TimestampValidator. When a client has a clock set a \
> few minutes in the future (or past), their timestamp  fails verification in the \
> verifyCreated method in the Timestamp, the return of message expired is misleading \
> and can cause a user to look in the wrong place. Maybe "The message timestamp is \
> out of range!?"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]