Configure ConnId locations

Syncope can be configured for using either local and remote connector bundles:

• local connector bundles are located somewhere in the same filesystem where the container running Syncope is deployed;
• remote connector bundles are provided via Java or .NET connector server.

While local connector bundles feature an easy setup, remote connector bundles allow enhanced deployment scenarios and are particularly useful when it is needed to deal with architectural security constraints or when a connector bundle requires to run on a specific platform OS (say MS Windows) while Syncope is deployed on another platform OS (say GNU/Linux).

connid.properties

This file (located at core/src/main/resources/connid.properties) holds the configuration for defining which ConnId locations (either local and remote) Syncope will be able to deal with.

The format is quite straightforward:

connid.locations=location1,\
location2,\
...
locationN

where each location is the string representation of an URI of the form

file:/path/to/directory/

for local locations or

connid://key@host:port

for remote non-SSL connector servers or

connids://key@host:port[?trustAllcerts=true]

for remote SSL connector servers, with optional flag to disable certificate check. Refer to Connid for how to work with Java or .NET connector servers.

Some examples

Single local location

connid.locations=file:/opt/syncope/bundles/

Single remote location

connid.locations=connid://sampleKey@windows2008:4554

Multiple locations

connid.locations=file:/opt/syncope/bundles/,\
file:/var/tmp/bundles/,\
connid://sampleKey@windows2008:4554,\
connids://anotherKey@windows2008:4559,\
connids://aThirdKey@linuxbox:9001?trustAllCerts=true