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/
