Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Migrating database from 2.2.7 to 3.0.4 results into wrong security settings for the users

web-app

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
dhvik
Replies (3)
helpful
0
not helpful

This is because of major changes to the security model of Gemini.

We suggest deleting all schemes, then depending on your situation, create global / project groups and assign them to new schemes you create.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Can't you supply a migration script that creates Project Groups of all current security schemes, attaches them to the new projects schemes and assigns the correct users to the Project Groups?

As now, we cannot upgrade since the users security assignments are all wrong...


dhvik
· 1
dhvik
helpful
0
not helpful

Unfortunately, we can not do that as the mogration can be done via gloabl or project groups.

Some customers prefare the global group approach and some have specific project admin so they prefer the project group approach.


Saar Cohen
· 5000
Saar Cohen