ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] [Resolved] (WSS-554) Improved error message for timestamp in the future
Date Tue, 15 Sep 2015 09:48:46 GMT


Colm O hEigeartaigh resolved WSS-554.
    Resolution: Fixed

> Improved error message for timestamp in the future
> --------------------------------------------------
>                 Key: WSS-554
>                 URL:
>             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
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message