[
https://issues.apache.org/jira/browse/SYNCOPE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152845#comment-17152845
]
Jim Lawhorn commented on SYNCOPE-1574:
--------------------------------------
I had written up a big response that detailed out how I getting different
results, but in the process discovered it to be an issue on my side. I think
it was the grooviness of the dynamic typing that was tripping me up. While I
was explicitly declaring the token to be String type, I was using a common
"response" variable that was dynamically typed and set to either the Map
returned by SYNC or the token value. If I change the script to return the
token directly on the GET_LATEST_SYNC_TOKEN action, I no longer have the issue.
Sorry for the trouble, i appreciate you taking the time to respond.
> 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)
