[Wsf-jira] [jira] Commented: (WSFPHP-454) ClockSkewBuffer always 0 making timestamp validation fail often

[siva prasad (JIRA)]

    [ https://wso2.org/jira/browse/WSFPHP-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42463#action_42463 ] 

siva prasad commented on WSFPHP-454:
------------------------------------

Hi,
                     1)  How to Integrate WSo2 ESB with IBM MQ series.
                     2) I think IBM MQ  take input request and response as a Flat File, if it Correct Who is going to Convert XML request cumming from wso2 ESB  to Flat File.
                     3) what are the Minimum Configuration Setting needs to integrate with MQ

Regards
sivaprasad.sompalle at saggezza.com

> ClockSkewBuffer always 0 making timestamp validation fail often
> ---------------------------------------------------------------
>
>                 Key: WSFPHP-454
>                 URL: https://wso2.org/jira/browse/WSFPHP-454
>             Project: WSO2 WSF/PHP
>          Issue Type: Bug
>          Components: WS-Policy Support
>    Affects Versions: 2.1.0
>         Environment: Debian 5.0.3, amd64, PHP 5.3.3-1ubuntu9 with Suhosin-Patch
>            Reporter: Pawel Puterla
>            Assignee: Nandika Jayawardana
>             Fix For: Current (nightly)
>
>         Attachments: ClockSkewBuffer.zip
>
>
> According to thread
> http://wso2.org/forum/thread/10421 
> jfaircloth and lcyhao.yahoo.com reported an issue with ClockSkewBuffer. I must report I have the same problem.
> Essentialy - the ClockSkewBuffer seems to be always set to 0 resulting often timestamp verification failure when client and server have different
> times.
> Verification stops on rampart_timestamp_token.c:181 with message:
> "Timestamp not valid: Created time is not valid" 
> According to nandika: "...but the ClockSkewBuffer option has not been added to the WSSecurityToken options.Could you raise a jira issue for this. "
> So...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira