preserveLastSync: is it required?

This topic has 0 replies, 1 voice, and was last updated 3 years, 7 months ago by [email protected].

  • Author
    Posts
  • #17959

    Hi all,

    after upgrading from 3.1 to 4.5 I notice an increased load on our repository, which is mostly due to “require(‘ui/onUpdateUser’).preserveLastSync(object, oldObject, request);” in managed_onUpdate.

    In the past it took one insert operation to managedobjects to create a new user, now it is one insert and 15 updates, due to 15 mappings, each updating preserveLastSync. And this results in an increase of audit-entries as well, since each updated lastSync-timestamp results in an audit-entry.

    Is there anything to be aware of? I’d like to disable it, but I’m not sure how or if lastSync is used at all.

    Yours,
    Patrick.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2021 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?