[jira] [Updated] (SYNCOPE-1105) Provide unique key for operations

["Francesco Chicchiriccò (Jira)" <ji...@apache.org>]

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

Francesco Chicchiriccò updated SYNCOPE-1105:
--------------------------------------------
      Component/s:     (was: console)
    Fix Version/s: 4.0.0
      Description: 
The operations performed by Syncope Core, either triggered via REST or by a Task / Report could be identified by a unique key.
Such key can then be used during log inspection to correlate events.

  was:
The operations driven by the ProvisioningManager (e.g. CREATE / UPDATE / DELETE about User / Group / Any Object entities) do not currently provide any mean to bind together the various activity involved, which generally are:

# CREATE / UPDATE / DELETE onto the internal storage via WorkflowAdapter
# propagation towards the assigned (direct and via group membership, when applicable) External Resources

If a unique key is generated for the ongoing operation, such key can be used to inspect logs and correlate events.

          Summary: Provide unique key for operations  (was: Provide unique key for ProvisioningManager operations)

> Provide unique key for operations
> ---------------------------------
>
>                 Key: SYNCOPE-1105
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1105
>             Project: Syncope
>          Issue Type: New Feature
>          Components: core
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 3.0.1, 4.0.0
>
>
> The operations performed by Syncope Core, either triggered via REST or by a Task / Report could be identified by a unique key.
> Such key can then be used during log inspection to correlate events.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)