[
https://issues.apache.org/jira/browse/SYNCOPE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152217#comment-17152217
]
Jim Lawhorn commented on SYNCOPE-1574:
--------------------------------------
I understand how this works, and I believe it to be a bug. I included the
modified sample script to demonstrate it's happening with the delivered
examples, which means it's not likely a code issue on my side.
When I run a GET_LATEST_SYNC_TOKEN, the logs look like:
06:28:47.505 INFO net.tirasa.connid.commons.scripted.AbstractScriptedConnector
- Entering GET_LATEST_SYNC_TOKEN Script. Object is: __ACCOUNT__
06:28:47.514 INFO net.tirasa.connid.commons.scripted.AbstractScriptedConnector
- New Token is 2020070606284701
06:28:47.514 INFO net.tirasa.connid.commons.scripted.AbstractScriptedConnector
- SYNC complete
When I run a subsequent pull action, I get:
06:37:01.414 INFO net.tirasa.connid.commons.scripted.AbstractScriptedConnector
- Entering SYNC Script. Object is: __ACCOUNT__
06:37:01.415 INFO net.tirasa.connid.commons.scripted.AbstractScriptedConnector
- Token is: -37
The value of the token in the SYNC should match the output of the
GET_LATEST_SYNC_TOKEN which is: 2020070606284701. I can't use the value being
sent and I don't know how it got set that way other than there is some process
in the REST connector which is modifying it. I'm using similar code in a
Scripted DB resource and do not have a problem getting the token back correctly
on a SYNC.
> 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)
