You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by "Noah Hansen ." <no...@gmail.com> on 2019/07/24 13:46:44 UTC
Keeping multiple connectors synced
Hi all,
I'm using syncope 2.1.4 and trying to find a way to sync connectors to each
other.
i.e. if we execute a push task to one, it will automatically execute that
same push task to the other.
I've been reading through the reference guide and can't seem to find
anything of that matter.
Thanks again,
Noah Hansen
Re: Keeping multiple connectors synced
Posted by "Noah Hansen ." <no...@gmail.com>.
This has been resolved
On Thu, Jul 25, 2019 at 2:10 PM Noah Hansen . <no...@gmail.com>
wrote:
> Hi again,
>
> Since you responded i decided to go ahead and delve into getting pull,
> push, and propagate tasks to start working. I was able to get pull working
> fine until recently nothing will work now. I'm running 2.1.4 through docker
> and have tried to reboot both syncope and docker multiple times. Pull
> doesn't ignore, create, or update anything. I don't even think it's able to
> find the ldaps at all at this point.
>
> I've made sure the ldap instance is on, made sure it connects through the
> connector using the heart button, and have tried re creating my resource
> and configuring it to where I got it to work.
>
> Let me know if you need any other info.
>
> thanks,
> -Noah Hansen
>
> On Thu, Jul 25, 2019 at 1:58 AM Francesco Chicchiriccò <
> ilgrosso@apache.org> wrote:
>
>> On 24/07/19 15:46, Noah Hansen . wrote:
>> > Hi all,
>> >
>> > I'm using syncope 2.1.4 and trying to find a way to sync connectors to
>> > each other.
>> > i.e. if we execute a push task to one, it will automatically execute
>> > that same push task to the other.
>> >
>> > I've been reading through the reference guide and can't seem to find
>> > anything of that matter.
>>
>> Hi,
>> Syncope supports both automatic and manual provisioning:
>>
>> * the former happens whenever a User, which is assigned to one or more
>> External Resources, is created / updated / deleted on Syncope via REST
>> or Admin Console; for example, updating one user's e-mail address will
>> generate propagations onto all associated Resources with e-mail defined
>> in Mapping;
>>
>> * the latter happens by creating and executing Push Tasks and is
>> disconnected from User CRUD; naturally Push Tasks can be scheduled to
>> occur regularly, if needed.
>>
>> There is no orchestration available for coordinating multiple Push
>> Tasks: in similar cases, I would suggest to implement a Custom Task [1]
>> where you can code the required logic.
>>
>> HTH
>> Regards.
>>
>> [1] http://syncope.apache.org/docs/2.1/reference-guide.html#tasks-custom
>>
>> --
>> 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/
>>
>>
Re: Keeping multiple connectors synced
Posted by "Noah Hansen ." <no...@gmail.com>.
Hi again,
Since you responded i decided to go ahead and delve into getting pull,
push, and propagate tasks to start working. I was able to get pull working
fine until recently nothing will work now. I'm running 2.1.4 through docker
and have tried to reboot both syncope and docker multiple times. Pull
doesn't ignore, create, or update anything. I don't even think it's able to
find the ldaps at all at this point.
I've made sure the ldap instance is on, made sure it connects through the
connector using the heart button, and have tried re creating my resource
and configuring it to where I got it to work.
Let me know if you need any other info.
thanks,
-Noah Hansen
On Thu, Jul 25, 2019 at 1:58 AM Francesco Chicchiriccò <il...@apache.org>
wrote:
> On 24/07/19 15:46, Noah Hansen . wrote:
> > Hi all,
> >
> > I'm using syncope 2.1.4 and trying to find a way to sync connectors to
> > each other.
> > i.e. if we execute a push task to one, it will automatically execute
> > that same push task to the other.
> >
> > I've been reading through the reference guide and can't seem to find
> > anything of that matter.
>
> Hi,
> Syncope supports both automatic and manual provisioning:
>
> * the former happens whenever a User, which is assigned to one or more
> External Resources, is created / updated / deleted on Syncope via REST
> or Admin Console; for example, updating one user's e-mail address will
> generate propagations onto all associated Resources with e-mail defined
> in Mapping;
>
> * the latter happens by creating and executing Push Tasks and is
> disconnected from User CRUD; naturally Push Tasks can be scheduled to
> occur regularly, if needed.
>
> There is no orchestration available for coordinating multiple Push
> Tasks: in similar cases, I would suggest to implement a Custom Task [1]
> where you can code the required logic.
>
> HTH
> Regards.
>
> [1] http://syncope.apache.org/docs/2.1/reference-guide.html#tasks-custom
>
> --
> 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/
>
>
Re: Keeping multiple connectors synced
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 24/07/19 15:46, Noah Hansen . wrote:
> Hi all,
>
> I'm using syncope 2.1.4 and trying to find a way to sync connectors to
> each other.
> i.e. if we execute a push task to one, it will automatically execute
> that same push task to the other.
>
> I've been reading through the reference guide and can't seem to find
> anything of that matter.
Hi,
Syncope supports both automatic and manual provisioning:
* the former happens whenever a User, which is assigned to one or more
External Resources, is created / updated / deleted on Syncope via REST
or Admin Console; for example, updating one user's e-mail address will
generate propagations onto all associated Resources with e-mail defined
in Mapping;
* the latter happens by creating and executing Push Tasks and is
disconnected from User CRUD; naturally Push Tasks can be scheduled to
occur regularly, if needed.
There is no orchestration available for coordinating multiple Push
Tasks: in similar cases, I would suggest to implement a Custom Task [1]
where you can code the required logic.
HTH
Regards.
[1] http://syncope.apache.org/docs/2.1/reference-guide.html#tasks-custom
--
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/