You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2024/11/18 07:52:00 UTC
[jira] [Assigned] (SYNCOPE-1829) Pull by subscription
[ https://issues.apache.org/jira/browse/SYNCOPE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò reassigned SYNCOPE-1829:
-----------------------------------------------
Assignee: Francesco Chicchiriccò
> Pull by subscription
> --------------------
>
> Key: SYNCOPE-1829
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1829
> Project: Syncope
> Issue Type: New Feature
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 4.0.0
>
>
> There have been a few use cases where Syncope was requested to "import" users by subscribing to some sort of queue, like as Apache Kafka / ActiveMQ, Google PubSub, etc.
> A more general mechanism can be implemented, to generate pull events (e.g. ConnId's {{SyncDelta}} objects) from messages received via queue subscription.
> Then we could provide one or more implementations, one for each queue technology - the ones mentioned above, but even more if needed.
> Also, there should be a flexible, extensible way to transform the message payload into a {{SyncDelta}} instance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)