[
https://issues.apache.org/jira/browse/SYNCOPE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152098#comment-17152098
]
Francesco Chicchiriccò commented on SYNCOPE-1574:
-------------------------------------------------
For further discussion, I invite you to [subscribe the user mailing
list|http://syncope.apache.org/mailing-lists]; after receiving the WELCOME
message, you will be enabled to send your inquiries there.
> Sync token is mangled in Rest Connector
> ---------------------------------------
>
> Key: SYNCOPE-1574
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1574
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 2.1.6
> Reporter: Jim Lawhorn
> Priority: Critical
> Attachments: SyncScript_Test.groovy
>
>
> The token value is being altered by the REST connector - the token value
> being set by GET_LATEST_SYNC_TOKEN is not the token value sent to the SYNC
> operation when performing a pull.
> Using the demo version, the token value being set is a date, however the
> value received back is "-37". This does not appear to be an issue with the
> DB Scripted connector. I'm unsure if this is a syncope problem or a connid
> problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
