[jira] [Commented] (SYNCOPE-1558) Configure WA delegated authn module to SAML IdPs via REST
[ https://issues.apache.org/jira/browse/SYNCOPE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095519#comment-17095519 ] Misagh Moayyed commented on SYNCOPE-1558: - PR finalized and ready. 4.0.1 SNAPSHOT of pac4j should contain the change, and the change is pushed into the next snapshot release of CAS. Next, will fine-tune the WA configuration with the next CAS snapshot to take advantage of latest pac4j changes for SAML IDP config. > Configure WA delegated authn module to SAML IdPs via REST > - > > Key: SYNCOPE-1558 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1558 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > When WA is configured to hand off authentication to an external SAML2 > identity provider via pac4j, pac4j expects a java keystore to be > created/present on disk that will be used by WA as a SAML SP to interact with > the IDP and to generate metadata, sign responses, etc. This keystore is > expected to be found on disk, and pac4j does not allow other options for > producing/fetching the keystore via REST. > Also, a number of other artifacts such as generation of SP metadata, etc > should be configurable over rest. > > Task is: > * Allow pac4j to open up its api/configuration to allow for keystore > fetching over rest > * Modify WA to use this configuration and produce keystore data over rest. > > Note that a similar and separate task may be created to handle the same > matter with delegated authn to OIDC OPs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [syncope] mat-ale commented on a change in pull request #178: [SYNCOPE-1555] Allow WA as SAMLs IdP to fetch metadata over REST
mat-ale commented on a change in pull request #178: URL: https://github.com/apache/syncope/pull/178#discussion_r417332912 ## File path: wa/starter/src/main/java/org/apache/syncope/wa/SyncopeCoreNotReadyException.java ## @@ -0,0 +1,25 @@ +/* Review comment: @mmoayyed What do you mean with "So perhaps we can just return `false` here"? According to your clarification I guess that one option could be to pull out the `getSyncopeClient()` from the `try/catch` and make it throw the blocking exception in order to block the execution (or just replace `Exception` with `SyncopeClientException` the same way I do in `RestfulSamlIdPMetadataLocator.java`). But about the `SyncopeCoreNotReadyException`, do you guys want to keep it or just throw a `RuntimeException` with `Syncope core is not yet ready to access requests` as message? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] mat-ale commented on a change in pull request #178: [SYNCOPE-1555] Allow WA as SAMLs IdP to fetch metadata over REST
mat-ale commented on a change in pull request #178: URL: https://github.com/apache/syncope/pull/178#discussion_r417332912 ## File path: wa/starter/src/main/java/org/apache/syncope/wa/SyncopeCoreNotReadyException.java ## @@ -0,0 +1,25 @@ +/* Review comment: @mmoayyed What do you mean with "So perhaps we can just return `false` here"? According to your clarification I guess that one option could be to pull out the `getSyncopeClient()` from the `try/catch` and make it throw the blocking exception in order to block the execution (or just replace the `Exception` with `SyncopeClientException` the same way I do in `RestfulSamlIdPMetadataLocator.java`). But about the `SyncopeCoreNotReadyException`, do you guys want to keep it or just throw a `RuntimeException` with `Syncope core is not yet ready to access requests` as message? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] mat-ale commented on a change in pull request #178: [SYNCOPE-1555] Allow WA as SAMLs IdP to fetch metadata over REST
mat-ale commented on a change in pull request #178: URL: https://github.com/apache/syncope/pull/178#discussion_r417332912 ## File path: wa/starter/src/main/java/org/apache/syncope/wa/SyncopeCoreNotReadyException.java ## @@ -0,0 +1,25 @@ +/* Review comment: @mmoayyed What do you mean with "So perhaps we can just return `false` here"? According to your clarification I guess that one option could be to pull out the `getSyncopeClient()` from the `try/catch` and make it throw the blocking exception in order to block the execution. But about the `SyncopeCoreNotReadyException`, do you guys want to keep it or just throw a `RuntimeException` with `Syncope core is not yet ready to access requests` as message? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [VOTE] Apache Syncope 2.0.15
+1 Best regards, Andrea Il 29/04/20 14:08, Francesco Chicchiriccò ha scritto: I've created a 2.0.15 release, with the following artifacts up for a vote: GIT source tag (2c668d5): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=2c668d5 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a09206954f5db6800555b7c2932f229026d926d4;hb=2c668d5 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.15/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1063/ Staging site (yes, same as for 2.1.6, not a typo): http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Dott. Andrea Patricelli Tel. +39 3204524292 Engineer @ Tirasa S.r.l. Viale Vittoria Colonna 97 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member
Re: [VOTE] Apache Syncope 2.1.6
+1 Best regards, Andrea Il 29/04/20 14:00, Francesco Chicchiriccò ha scritto: I've created a 2.1.6 release, with the following artifacts up for a vote: GIT source tag (95f09c0): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=95f09c0 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=95f09c0 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.6/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1062/ Staging site: http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Dott. Andrea Patricelli Tel. +39 3204524292 Engineer @ Tirasa S.r.l. Viale Vittoria Colonna 97 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member
Re: [VOTE] Apache Syncope 2.1.6
+1 (binding) Regards JB > Le 29 avr. 2020 à 14:00, Francesco Chicchiriccò a écrit > : > > I've created a 2.1.6 release, with the following artifacts up for a vote: > > GIT source tag (95f09c0): > https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=95f09c0 > > List of changes: > https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=95f09c0 > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/2.1.6/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1062/ > > Staging site: > http://syncope.apache.org/2.1.6/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ >
[GitHub] [syncope] mmoayyed commented on a change in pull request #178: [SYNCOPE-1555] Allow WA as SAMLs IdP to fetch metadata over REST
mmoayyed commented on a change in pull request #178: URL: https://github.com/apache/syncope/pull/178#discussion_r417290694 ## File path: wa/starter/src/main/java/org/apache/syncope/wa/SyncopeCoreNotReadyException.java ## @@ -0,0 +1,25 @@ +/* Review comment: Strictly speaking, this is not required here because we'd be making an assumption that core is in fact ready by the time this method is called (and is only called once the app is ready). If by then core is not ready, we should likely consider that a catastrophic event and end the app, specially because this (metadata, etc) is not the sort of thing one can ignore unlike other places. So perhaps we can just return `false` here, but... ..more importantly, I see the catch clause that traps `Exception`, and by extension this one, just logs a warning. I don't think that's right; at the point in the lifetime of the app when this method is called, core must be ready. Its unavailability should halt the app and present an error (more than a warning). ## File path: wa/starter/src/main/java/org/apache/syncope/wa/SyncopeCoreNotReadyException.java ## @@ -0,0 +1,25 @@ +/* Review comment: Strictly speaking, this is not required here because we'd be making an assumption that core is in fact ready by the time this method is called (and is only called once the app is ready). If by then core is not ready, we should likely consider that a catastrophic event and end the app, specially because this (metadata, etc) is not the sort of thing one can ignore unlike other places. So perhaps we can just return `false` here, but... ...more importantly, I see the catch clause that traps `Exception`, and by extension this one, just logs a warning. I don't think that's right; at the point in the lifetime of the app when this method is called, core must be ready. Its unavailability should halt the app and present an error (more than a warning). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [VOTE] Apache Syncope 2.0.15
Il 29/04/20 14:08, Francesco Chicchiriccò ha scritto: I've created a 2.0.15 release, with the following artifacts up for a vote: GIT source tag (2c668d5): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=2c668d5 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a09206954f5db6800555b7c2932f229026d926d4;hb=2c668d5 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.15/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1063/ Staging site (yes, same as for 2.1.6, not a typo): http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
Re: [VOTE] Apache Syncope 2.1.6
Il 29/04/20 14:00, Francesco Chicchiriccò ha scritto: I've created a 2.1.6 release, with the following artifacts up for a vote: GIT source tag (95f09c0): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=95f09c0 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=95f09c0 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.6/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1062/ Staging site: http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. +1 Regards -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/index.html?pk_campaign=email_kwd=fm Apache Syncope PMC http://people.apache.org/~fmartelli/
[VOTE] Apache Syncope 2.0.15
I've created a 2.0.15 release, with the following artifacts up for a vote: GIT source tag (2c668d5): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=2c668d5 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a09206954f5db6800555b7c2932f229026d926d4;hb=2c668d5 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.15/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1063/ Staging site (yes, same as for 2.1.6, not a typo): http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.6
I've created a 2.1.6 release, with the following artifacts up for a vote: GIT source tag (95f09c0): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=95f09c0 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=95f09c0 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.6/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1062/ Staging site: http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Passed: apache/syncope#6401 (syncope-2.0.15 - ed7a41d)
Build Update for apache/syncope - Build: #6401 Status: Passed Duration: 18 mins and 52 secs Commit: ed7a41d (syncope-2.0.15) Author: Francesco Chicchiriccò Message: prepare release syncope-2.0.15 View the changeset: https://github.com/apache/syncope/compare/09c60772df15^...ed7a41d182bd View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/680953472?utm_medium=notification_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Errored: apache/syncope#6402 (2_0_X - 9eae01f)
Build Update for apache/syncope - Build: #6402 Status: Errored Duration: 18 mins and 29 secs Commit: 9eae01f (2_0_X) Author: Francesco Chicchiriccò Message: prepare for next development iteration View the changeset: https://github.com/apache/syncope/compare/81ebbb81e5f2...9eae01f90b95 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/680954891?utm_medium=notification_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Passed: apache/syncope#6399 (syncope-2.1.6 - a1200e1)
Build Update for apache/syncope - Build: #6399 Status: Passed Duration: 34 mins and 2 secs Commit: a1200e1 (syncope-2.1.6) Author: Francesco Chicchiriccò Message: prepare release syncope-2.1.6 View the changeset: https://github.com/apache/syncope/commit/a1200e18dacc View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/680928486?utm_medium=notification_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Passed: apache/syncope#6398 (2_1_X - a2a9417)
Build Update for apache/syncope - Build: #6398 Status: Passed Duration: 36 mins and 27 secs Commit: a2a9417 (2_1_X) Author: Francesco Chicchiriccò Message: Attempting to fix (again) Tycho View the changeset: https://github.com/apache/syncope/compare/864e7e0eda91...a2a94178ad3d View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/680909455?utm_medium=notification_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Passed: apache/syncope#6397 (2_1_X - 864e7e0)
Build Update for apache/syncope - Build: #6397 Status: Passed Duration: 34 mins and 59 secs Commit: 864e7e0 (2_1_X) Author: Francesco Chicchiriccò Message: Attempting to fix (again) Tycho View the changeset: https://github.com/apache/syncope/compare/ff9819b4ef70...864e7e0eda91 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/680909080?utm_medium=notification_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
[jira] [Updated] (SYNCOPE-1137) Save button on resource creation is disabled after adding an object type
[ https://issues.apache.org/jira/browse/SYNCOPE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1137: Fix Version/s: (was: 2.1.6) (was: 2.0.15) 2.1.7 2.0.16 > Save button on resource creation is disabled after adding an object type > > > Key: SYNCOPE-1137 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1137 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.3 >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > # Login on Admin Console > # Go to Topology and edit an existing resource > # Click on Edit Provisioning Rules > # Add an object type (+ button) and then finish > # Sometimes (randomically) the save button is disabled and you cannot save > the modifications. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1403) Netbeans IDE plugin does not recognize classpath dependencies while editing .groovy classes
[ https://issues.apache.org/jira/browse/SYNCOPE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1403: Fix Version/s: (was: 2.1.6) 2.1.7 > Netbeans IDE plugin does not recognize classpath dependencies while editing > .groovy classes > --- > > Key: SYNCOPE-1403 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1403 > Project: Syncope > Issue Type: Bug > Components: ide >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.1.7, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1549) Groups select opens a popup when removing a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1549: Fix Version/s: (was: 2.1.6) (was: 2.0.15) 2.1.7 2.0.16 > Groups select opens a popup when removing a group > - > > Key: SYNCOPE-1549 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1549 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.14, 2.1.5 > Environment: Google Chrome 80.0.3987.132 > Mozilla Firefox 74.0 >Reporter: Andrea Patricelli >Priority: Major > Fix For: 2.0.16, 2.1.7 > > > # Open enduser login page and click on "Registration" > # Go to the Groups step and add a group > # Remove the group just added and you'll notice on Chrome a popup and on > FIrefox an error page showing undefined JavaScript execution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-917) Add use cases to reference guide
[ https://issues.apache.org/jira/browse/SYNCOPE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-917: --- Fix Version/s: (was: 2.1.6) (was: 2.0.15) 2.1.7 2.0.16 > Add use cases to reference guide > > > Key: SYNCOPE-917 > URL: https://issues.apache.org/jira/browse/SYNCOPE-917 > Project: Syncope > Issue Type: Task > Components: documentation >Reporter: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > Introduce, in a dedicated chapter at the end of the reference guide, some > reference use cases; for example: > * LDAP sync > * GoogleApps sync > * Active Directory sync > and more, migrating from wiki pages: > * > https://cwiki.apache.org/confluence/display/SYNCOPE/Configure+a+PasswordExpirationJob > * > https://cwiki.apache.org/confluence/display/SYNCOPE/Synchronize+Active+Directory+with+SQL+database -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1105) Provide unique key for ProvisioningManager operations
[ 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.6) (was: 2.0.15) 2.1.7 2.0.16 > 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.16, 2.1.7, 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)
