You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Jim Lawhorn (Jira)" <ji...@apache.org> on 2020/07/06 13:03:00 UTC

[jira] [Updated] (SYNCOPE-1574) Sync token is mangled in Rest Connector

     [ https://issues.apache.org/jira/browse/SYNCOPE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Lawhorn updated SYNCOPE-1574:
---------------------------------
    Attachment: SyncScript_Test.groovy

> 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)