[
https://issues.apache.org/jira/browse/SYNCOPE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1105:
--------------------------------------------
Description:
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.
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 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.
> 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ò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 3.0.1
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
