Relevant changes

MD5 is not supported any more

SYNCOPE-51 removed MD5 from supported password cipher algorithm.

This means that:

1. password.cipher.algorithm must be set to something different (say SHA1) in SyncopeConf table
2. any row in SyncopeUser table with cipherAlgorithm=MD5 must be set to something different (say SHA1); moreover, all users must change their own password

Role provisioning

Role provisioning (provided by SYNCOPE-172 and related) changed the way how the schema mapping is stored by removing the SchemaMapping table and introducing the following new tables:

• UMapping
• UMappingItem
• RMapping
• RMappingItem

Quartz upgraded to 2.1.X

Syncope now features the latest version of Quartz (as per SYNCOPE-93).

Remove any QRTZ_* table from the database: such tables will be re-created at next startup.

New mandatory conf param 'notificationjob.cronExpression'

As per SYNCOPE-216, you can specify when the NotificationJob will run.

Add a row to SyncopeConf table with key = notificationjob.cronExpression and your chosen cron expression as value.

Reference and some examples of cron expressions are provided in Quartz website.

Changes in Task table

• SYNCOPE-144 introduced two additional columns in Task table:

  name VARCHAR(255), description VARCHAR(255)

• Change any value from org.apache.syncope.core.scheduling.SyncJob to org.apache.syncope.core.sync.SyncJob of the jobClassName column

Moreover, SYNCOPE-186 renamed jobActionsClassName to actionsClassName

Changes in SyncopeRole table

SYNCOPE-225 introduced three additional columns in SyncopeRole table:

inheritOwner INTEGER,
ROLEOWNER_ID BIGINT,
USEROWNER_ID BIGINT

Changes in ConnInstance table

SYNCOPE-279 introduced an additional column in ConnInstance table:

connRequestTimeout INTEGER

Changes in ExternalResource table

• ExternalResource.forceMandatoryConstraint renamed as ExternalResource.enforceMandatoryCondition
• ExternalResource has now an additional column

  actionsClassName VARCHAR(255)

Changes in Entitlement table

• SYNCOPE-319 introduced the new CONNECTOR_RELOAD entitlement
• SYNCOPE-331 renamed RESOURCE_GETOBJECT as RESOURCE_GETCONNECTOROBJECT

Suggested procedure

Make the TODO tab empty

1. Approve or reject any pending approval
2. Manage any pending user request

Backup

Make full backup of

1. the internal storage
2. your 1.0.X project's (the one created from archetype) sources
3. configured bundles and logs directories

The new 1.1.X project

1. create a new 1.1.X project
2. copy any existing Java class you have developed for your 1.0.X project and make necessary adaptations
3. include any connector bundle you might have added in your 1.0.X project