Migrating database from 2.2.7 to 3.0.4 results into wrong security settings for the users
I tried to migrate our current 2.2.7 Gemini to the latest 3.0.4 version.
The migration sql scripts passes without errors but the user/project security mappings are all wrong.
In the 2.2.7 db we have mapped projects with a security schemes and connected different users to them.
When the migration is done we get Global groups named like the schemas in the old db, but the members of the global groups is ALL of the users ever using that schema...
So if Project A has a Project Administration (schema) named User A and Project B has the User B as Project Administration, then the Global Group Project Administration has both User A and B as members.
If we then look at the Security Scheme (this is not true for all projects but for some of them (we have 50+ projects)), some are using the global groups to assign rights to the projects. In some of the projects, the mapping is done per user, but in some the mapping is done to the global groups that contains the incorrect users.. Why is the schema using the global groups (that contains wrong users)?
What should we do to perform a correct update?
/Dan
dhvik
· 1 |
|
Tuesday, September 23, 2008, 10:58:07 PM |