THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Note | ||
|---|---|---|
| ||
The content below is for Apache Syncope <= 1.2 - for later versions the Reference Guide is available. |
| Table of Contents | ||
|---|---|---|
|
Syncope uses entities like connectors bundles, connector instances and external resources to synchronize user accounts with and propagate to external systems.
This page clarifies what the responsibility and scope of each of these entities are.
...
Connector bundles are the components that are able to connect to classes of systems when configured correctly and told to do so. They are not bound to Syncope specifically, as they are part of the separate framework ConnId, but they can be plugged into a deployed Syncope system.
...
Resources are meant to encapsulate all information about how Syncope will use connector instances for its own purpose (i.e. provisioning). That's why, when defining a Resource, you can define how the data provided by a certain connector are mapped to user attributes, managed by Syncope. The latter is called the schema mapping.
Resources are used both for synchronization and for propagation (i.e. inbound and outbound changes); the two different use cases can be described like this, using the terms of Syncope:
- users (and roles, starting from release 1.1.0) stored in an external resource can be synchronized to Syncope using a connector instance
- users (and roles, starting from release 1.1.0) stored in Syncope can be propagated to external resources using connector instances.