Fabio Martelli created SYNCOPE-1757: ---------------------------------------
Summary: Misalignment between SyncTokenSerializer and SyncTokenDeserializer in case of token given as a clear string Key: SYNCOPE-1757 URL: https://issues.apache.org/jira/browse/SYNCOPE-1757 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.3 Reporter: Fabio Martelli Fix For: 3.0.4 If resource connector provides a syncToken as a clear string and if this string is Base64 deserializable (i.e.AD uSNChanged "1934664") than serialization works fine ("syncToken":"\{\"value\":\"1934664\"}") but deserialization needed to ask for a new incremental PULL. In fact in this case the value is deserialized as a byte array because deserialized Base64. This behaviour cause the failure of the incremental PULL. [https://github.com/apache/syncope/blob/3_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/SyncTokenDeserializer.java] [https://github.com/apache/syncope/blob/3_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/SyncTokenSerializer.java] -- This message was sent by Atlassian Jira (v8.20.10#820010)