[jira] [Commented] (SYNCOPE-1614) Convert SyncopeService into Spring Boot's InfoContributor
[
https://issues.apache.org/jira/browse/SYNCOPE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17629015#comment-17629015
]
ASF subversion and git services commented on SYNCOPE-1614:
--
Commit c9b5da8b7142515f993e5a4544551374ff77711c in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=c9b5da8b71 ]
[SYNCOPE-1614] Avoid Console loading failure when git information is not
available through Core actuator/info
> Convert SyncopeService into Spring Boot's InfoContributor
> -
>
> Key: SYNCOPE-1614
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1614
> Project: Syncope
> Issue Type: Improvement
> Components: console, core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 3.0.0-M0
>
>
> SyncopeService REST endpoints should be converted into standard Spring Boot's
> {{InfoContributor}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1621) Allow export for individual items in XML
[ https://issues.apache.org/jira/browse/SYNCOPE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1621: Fix Version/s: 3.0.1 (was: 3.0.0) > Allow export for individual items in XML > - > > Key: SYNCOPE-1621 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1621 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Andrea Patricelli >Priority: Major > Fix For: 3.0.1 > > > Provide a functionality in the admin console (and from REST) that allows one > to view the XML configuration of an individual item. For example, an user > would be interested in seeing the XML representation of the new configuration > parameter, or it might be a user object, group, provisioning rules, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1662: Fix Version/s: 3.0.1 (was: 3.0.0) > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.1 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1617) LiveSync
[ https://issues.apache.org/jira/browse/SYNCOPE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1617: Fix Version/s: 3.0.1 (was: 3.0.0) > LiveSync > > > Key: SYNCOPE-1617 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1617 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.1 > > > [Debezium|https://debezium.io/] provides a mean to transform changes from > RDBMS, MongoDB and Cassandra into Kafka messages. > This tool can be leveraged to implement a listener-like approach to enable a > "live-sync" mechanism from External Resources not requiring ConnId. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (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ò closed SYNCOPE-917. -- Resolution: Fixed This issue has remained stale for years, closing. > 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 > > 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.20.10#820010)
[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: 3.0.1 (was: 3.0.0) > 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: 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 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.20.10#820010)
[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: 3.0.0) > 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 > > 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.20.10#820010)
[jira] [Updated] (SYNCOPE-1592) Propagation task executions and no-SQL persistence
[ https://issues.apache.org/jira/browse/SYNCOPE-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1592: Fix Version/s: 3.0.1 (was: 3.0.0) > Propagation task executions and no-SQL persistence > -- > > Key: SYNCOPE-1592 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1592 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.16, 2.1.7 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 3.0.1 > > > It would be very nice to use the actual Elasticsearch persistence extension > to persist and search also propagation tasks. It would be an useful feature > for environments with an huge number of propagation tasks and, moreover, > would give the ability to make fuzzy searches on propagation tasks and > especially executions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1696) Audit Elasticsearch persistence
[ https://issues.apache.org/jira/browse/SYNCOPE-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1696. - Resolution: Fixed > Audit Elasticsearch persistence > --- > > Key: SYNCOPE-1696 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1696 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 3.0.0-M0 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: elasticsearch > Fix For: 2.1.13, 3.0.0 > > > Give the possibility to switch the audit messages persistence on > Elasticsearch, instead of the Syncope database. This will improve search > performances and give more powerful search features. > Besides the main goal there could be also some query improvements to > implement, like passing more that on type or category in the AuditQuery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1696) Audit Elasticsearch persistence
[ https://issues.apache.org/jira/browse/SYNCOPE-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628852#comment-17628852 ] ASF subversion and git services commented on SYNCOPE-1696: -- Commit f91f5c00ab3808234f1da8a31b13d4b78b76f209 in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=f91f5c00ab ] [SYNCOPE-1696] Adding support to manage Audit entries via Elasticsearch (#388) > Audit Elasticsearch persistence > --- > > Key: SYNCOPE-1696 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1696 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 3.0.0-M0 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Labels: elasticsearch > Fix For: 2.1.13, 3.0.0 > > > Give the possibility to switch the audit messages persistence on > Elasticsearch, instead of the Syncope database. This will improve search > performances and give more powerful search features. > Besides the main goal there could be also some query improvements to > implement, like passing more that on type or category in the AuditQuery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [syncope] ilgrosso merged pull request #388: [SYNCOPE-1696] Adding support to manage Audit entries via Elasticsearch
ilgrosso merged PR #388: URL: https://github.com/apache/syncope/pull/388 -- 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. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SYNCOPE-1705) Deprecate SchedulingPullActions
[
https://issues.apache.org/jira/browse/SYNCOPE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628725#comment-17628725
]
ASF subversion and git services commented on SYNCOPE-1705:
--
Commit ae4b85b2e733b605e6bb683c9a8fcbb690bae09c in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=ae4b85b2e7 ]
[SYNCOPE-1705] Removing deprecated SchedulingPullActions
> Deprecate SchedulingPullActions
> ---
>
> Key: SYNCOPE-1705
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1705
> Project: Syncope
> Issue Type: Improvement
> Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 3.0.0-M2
>
>
> The class {{SchedulingPullActions}} has been used so far when, at the end of
> a Pull Task's execution, some logic needed to be executed, which required the
> entities pulled to be flushed to the internal storage.
> Typical use case is
> [LDAPMembershipPullActions|https://github.com/apache/syncope/blob/syncope-3.0.0-M1/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/pushpull/LDAPMembershipPullActions.java]
> which, in its {{afterAll()}} method, is scheduling
> [SetUMembershipsJob|https://github.com/apache/syncope/blob/syncope-3.0.0-M1/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/SetUMembershipsJob.java]
> to update the pulled users so that they become members of the pulled groups,
> matching the similar relationships existing in LDAP.
> Such scheduling approach has proven to be problematic, especially because the
> job scheduled at the end of a pull task execution cannot be controlled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
