You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Timo Hatakka <ti...@helsinki.fi> on 2013/11/18 15:37:14 UTC
Virtual attributes with off line resources
Hi,
the concept of virtual attributes in Syncope is fine. However, one have
somehow to be prepared for the situation that some source resource is off
line. Any ideas to how to implement it?
And on the other hand, how does Syncope process provisioning errors which
can happen every now and then?
Regards,
Timo
Re: Virtual attributes with off line resources
Posted by Fabio Martelli <fa...@gmail.com>.
Il 19/11/2013 07:42, Timo-V Hatakka ha scritto:
> Hi,
>
>>>> the concept of virtual attributes in Syncope is fine. However, one
>>>> have
>>>> somehow to be prepared for the situation that some source resource
>>>> is off
>>>> line. Any ideas to how to implement it?
>>>
>>> There is a virtual attribute cache in place with purpose of
>>> minimizing resource access for fetching virtual attribute values
>>> which also supports dealing with offline resources.
>>> Unfortunately, I don't think that any specific documentation about
>>> this is available: Fabio, can you confirm?
>> Hi, I confirm.
>> The expiring time of this cache is short and fixed (just what we need
>> to improve performance).
>> May be it can be extended in order to perform cleaning if and only if
>> updated value can be retrieved.
>
> Cache is for performance, it is OK. However we have to somehow catch
> the situation that a virtual attribute which sould be available is not.
Hi Timo, you are right.
I've just opened the following new issue.
https://issues.apache.org/jira/browse/SYNCOPE-442
Best regards,
F.
>
> Regards,
>
> Timo
>
>>>
>>>> And on the other hand, how does Syncope process provisioning errors
>>>> which
>>>> can happen every now and then?
>>>
>>> For each propagation operation, Syncope creates a propagation task
>>> that encapsulates the whole data needed to perform the actual
>>> operation (create, update, delete) on the external resource, than
>>> executes it immediately.
>>> The status of actual propagation on each resource associated to the
>>> user (or the role) being processed is then reported.
>>> If the execution fails for any reason, the task is still available
>>> there for re-execution.
>>>
>>> Hope this clarifies.
>>> Regards.
>>>
>>
>>
>> --
>> Fabio Martelli
>>
>> Tirasa - Open Source Excellence
>> http://www.tirasa.net/
>>
>> Apache Syncope PMC
>> http://people.apache.org/~fmartelli/
>
>
>
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
Re: Virtual attributes with off line resources
Posted by Fabio Martelli <fa...@gmail.com>.
Il 19/11/2013 07:42, Timo-V Hatakka ha scritto:
> Hi,
>
>>>> the concept of virtual attributes in Syncope is fine. However, one
>>>> have
>>>> somehow to be prepared for the situation that some source resource
>>>> is off
>>>> line. Any ideas to how to implement it?
>>>
>>> There is a virtual attribute cache in place with purpose of
>>> minimizing resource access for fetching virtual attribute values
>>> which also supports dealing with offline resources.
>>> Unfortunately, I don't think that any specific documentation about
>>> this is available: Fabio, can you confirm?
>> Hi, I confirm.
>> The expiring time of this cache is short and fixed (just what we need
>> to improve performance).
>> May be it can be extended in order to perform cleaning if and only if
>> updated value can be retrieved.
>
> Cache is for performance, it is OK. However we have to somehow catch
> the situation that a virtual attribute which sould be available is not.
Hi Timo, you are right.
I've just opened the following new issue.
https://issues.apache.org/jira/browse/SYNCOPE-442
Best regards,
F.
>
> Regards,
>
> Timo
>
>>>
>>>> And on the other hand, how does Syncope process provisioning errors
>>>> which
>>>> can happen every now and then?
>>>
>>> For each propagation operation, Syncope creates a propagation task
>>> that encapsulates the whole data needed to perform the actual
>>> operation (create, update, delete) on the external resource, than
>>> executes it immediately.
>>> The status of actual propagation on each resource associated to the
>>> user (or the role) being processed is then reported.
>>> If the execution fails for any reason, the task is still available
>>> there for re-execution.
>>>
>>> Hope this clarifies.
>>> Regards.
>>>
>>
>>
>> --
>> Fabio Martelli
>>
>> Tirasa - Open Source Excellence
>> http://www.tirasa.net/
>>
>> Apache Syncope PMC
>> http://people.apache.org/~fmartelli/
>
>
>
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
Re: Virtual attributes with off line resources
Posted by Timo-V Hatakka <ti...@helsinki.fi>.
Hi,
>>> the concept of virtual attributes in Syncope is fine. However, one have
>>> somehow to be prepared for the situation that some source resource is off
>>> line. Any ideas to how to implement it?
>>
>> There is a virtual attribute cache in place with purpose of
>> minimizing resource access for fetching virtual attribute values
>> which also supports dealing with offline resources.
>> Unfortunately, I don't think that any specific documentation about
>> this is available: Fabio, can you confirm?
> Hi, I confirm.
> The expiring time of this cache is short and fixed (just what we
> need to improve performance).
> May be it can be extended in order to perform cleaning if and only
> if updated value can be retrieved.
Cache is for performance, it is OK. However we have to somehow catch
the situation that a virtual attribute which sould be available is not.
Regards,
Timo
>>
>>> And on the other hand, how does Syncope process provisioning errors which
>>> can happen every now and then?
>>
>> For each propagation operation, Syncope creates a propagation task
>> that encapsulates the whole data needed to perform the actual
>> operation (create, update, delete) on the external resource, than
>> executes it immediately.
>> The status of actual propagation on each resource associated to the
>> user (or the role) being processed is then reported.
>> If the execution fails for any reason, the task is still available
>> there for re-execution.
>>
>> Hope this clarifies.
>> Regards.
>>
>
>
> --
> Fabio Martelli
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Apache Syncope PMC
> http://people.apache.org/~fmartelli/
Re: Virtual attributes with off line resources
Posted by Fabio Martelli <fa...@gmail.com>.
Il 18/11/2013 17:47, Francesco Chicchiriccò ha scritto:
> On 18/11/2013 15:37, Timo Hatakka wrote:
>> Hi,
>>
>> the concept of virtual attributes in Syncope is fine. However, one have
>> somehow to be prepared for the situation that some source resource is
>> off
>> line. Any ideas to how to implement it?
>
> There is a virtual attribute cache in place with purpose of minimizing
> resource access for fetching virtual attribute values which also
> supports dealing with offline resources.
> Unfortunately, I don't think that any specific documentation about
> this is available: Fabio, can you confirm?
Hi, I confirm.
The expiring time of this cache is short and fixed (just what we need to
improve performance).
May be it can be extended in order to perform cleaning if and only if
updated value can be retrieved.
>
>> And on the other hand, how does Syncope process provisioning errors
>> which
>> can happen every now and then?
>
> For each propagation operation, Syncope creates a propagation task
> that encapsulates the whole data needed to perform the actual
> operation (create, update, delete) on the external resource, than
> executes it immediately.
> The status of actual propagation on each resource associated to the
> user (or the role) being processed is then reported.
> If the execution fails for any reason, the task is still available
> there for re-execution.
>
> Hope this clarifies.
> Regards.
>
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
Re: Virtual attributes with off line resources
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 18/11/2013 15:37, Timo Hatakka wrote:
> Hi,
>
> the concept of virtual attributes in Syncope is fine. However, one have
> somehow to be prepared for the situation that some source resource is off
> line. Any ideas to how to implement it?
There is a virtual attribute cache in place with purpose of minimizing
resource access for fetching virtual attribute values which also
supports dealing with offline resources.
Unfortunately, I don't think that any specific documentation about this
is available: Fabio, can you confirm?
> And on the other hand, how does Syncope process provisioning errors which
> can happen every now and then?
For each propagation operation, Syncope creates a propagation task that
encapsulates the whole data needed to perform the actual operation
(create, update, delete) on the external resource, than executes it
immediately.
The status of actual propagation on each resource associated to the user
(or the role) being processed is then reported.
If the execution fails for any reason, the task is still available there
for re-execution.
Hope this clarifies.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/