[
https://issues.apache.org/jira/browse/SYNCOPE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984432#comment-16984432
]
Francesco Chicchiriccò commented on SYNCOPE-1105:
-------------------------------------------------
CXF's `ExchangeId` could be used for such a purpose, at least for operations
originated via REST - see
https://github.com/apache/cxf/blob/3.2.x-fixes/rt/features/logging/src/main/java/org/apache/cxf/ext/logging/AbstractLoggingInterceptor.java#L91-L96
> 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.15, 2.1.6, 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
(v8.3.4#803005)
