[
https://issues.apache.org/jira/browse/SYNCOPE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-753:
-------------------------------------------
Description:
Discuss and define a procedure for migrating Syncope 1.2 deployments to 2.0,
and build helping tools for the purpose.
Essentially, we need:
# a tool generating (mostly) valid {{*Content.xml}} in 2.0 format, taking a
1.2 {{content.xml}} (ideally exported from a 1.2 deployment)
# a "Syncope" ConnId connector which can be used to pull users and groups from
an existing 1.2 deployment
# a reference migration procedure to follow
The idea is that, given an existing 1.2 deployment, one will:
# generate a new 2.0 project
# export {{content.xml}} from 1.2 deployment
# run the migration tool to convert most of {{content.xml}} into some
{{MasterContent.xml}} - there are some items which cannot be directly migrated,
as virtual schemas and related mappings
# put the generated {{MasterContent.xml}} under
{{core/src/test/resources/domains}} in the new 2.0 project
# run the new 2.0 project in embedded mode while watching all logs - if errors
are found, make appropriate corrections into
{{core/src/test/resources/domains/MasterContent.xml}} - this might involve
migrate 1.2 customized classes into their respective 2.0 counterparts
# once errors are gone, access the admin console in embedded mode and look if
every configuration item is at its place (schema, connectors, resources,
mappings, notifications, ...)
# manually add the items that cannot be automatically migrated
# if using delegated administration, reconstruct roles and entitlements under
the [new security
model|https://cwiki.apache.org/confluence/display/SYNCOPE/[DISCUSS]+Realms#id-[DISCUSS]Realms-Newsecuritymodel]
# verify that all operations (CRUD / propagate / synchronize / push) about
users and roles in 1.2 are now working (CRUD / propagate / pull / push) with
users and groups in 2.0
was:Discuss and define a procedure for migrating Syncope 1.2 deployments to
2.0, and build helping tools for the purpose.
> Settle how to migrate from 1.2
> ------------------------------
>
> Key: SYNCOPE-753
> URL: https://issues.apache.org/jira/browse/SYNCOPE-753
> Project: Syncope
> Issue Type: Task
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Discuss and define a procedure for migrating Syncope 1.2 deployments to 2.0,
> and build helping tools for the purpose.
> Essentially, we need:
> # a tool generating (mostly) valid {{*Content.xml}} in 2.0 format, taking a
> 1.2 {{content.xml}} (ideally exported from a 1.2 deployment)
> # a "Syncope" ConnId connector which can be used to pull users and groups
> from an existing 1.2 deployment
> # a reference migration procedure to follow
> The idea is that, given an existing 1.2 deployment, one will:
> # generate a new 2.0 project
> # export {{content.xml}} from 1.2 deployment
> # run the migration tool to convert most of {{content.xml}} into some
> {{MasterContent.xml}} - there are some items which cannot be directly
> migrated, as virtual schemas and related mappings
> # put the generated {{MasterContent.xml}} under
> {{core/src/test/resources/domains}} in the new 2.0 project
> # run the new 2.0 project in embedded mode while watching all logs - if
> errors are found, make appropriate corrections into
> {{core/src/test/resources/domains/MasterContent.xml}} - this might involve
> migrate 1.2 customized classes into their respective 2.0 counterparts
> # once errors are gone, access the admin console in embedded mode and look
> if every configuration item is at its place (schema, connectors, resources,
> mappings, notifications, ...)
> # manually add the items that cannot be automatically migrated
> # if using delegated administration, reconstruct roles and entitlements
> under the [new security
> model|https://cwiki.apache.org/confluence/display/SYNCOPE/[DISCUSS]+Realms#id-[DISCUSS]Realms-Newsecuritymodel]
> # verify that all operations (CRUD / propagate / synchronize / push) about
> users and roles in 1.2 are now working (CRUD / propagate / pull / push) with
> users and groups in 2.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
