syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Created] (SYNCOPE-1105) Provide unique key for ProvisioningManager operations
Date Wed, 07 Jun 2017 08:40:18 GMT
Francesco Chicchiriccò created SYNCOPE-1105:
-----------------------------------------------

             Summary: 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ò
             Fix For: 2.0.4, 2.1.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
(v6.3.15#6346)

Mime
View raw message