[jira] [Updated] (SYNCOPE-1105) Provide unique key for ProvisioningManager 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:
--------------------------------------------
    Fix Version/s:     (was: 2.1.2)
                       (was: 2.0.11)
                   2.1.3
                   2.0.12

> Provide unique key for ProvisioningManager operations
> -----------------------------------------------------
>
>                 Key: SYNCOPE-1105
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1105
>             Project: Syncope
>          Issue Type: New Feature
>          Components: console, core
>            Reporter: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.0.12, 2.1.3, 3.0.0
>
>
> 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 also associated to the audit entries and notification messages (when enabled).
> This would allow, for example, to expose a new REST endpoint for querying the Audit table.
> Sample use case: trace what happens when creating user via REST with asynchronous propagations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)