Move of Ivy Security System to Entra ID leading to username change

costifab

Hi Axon Ivy Team

I have a question on what the best practice, the scenario is as following:

We are migrating an application from v8 to v12
There will be a completely new environment for this
We are planning to take over what we have, system db, business db, files and so on

Now here comes the catch, on the v8 environment there is only an Ivy Security System, but on v12 we'd like to connect to Entra ID. Coming with this, the username won't be the same anymore, as they are using an attribute right now which doesn't make sense anymore to use on the v12 and the new environment, it shall newly be the mail address.

Given that, what is the best practice to tackle this situation? Here are some topics I know should be considered:

Reassignment of existing tasks
Reassignment of done tasks or rather task workers (they are needed for displaying the history) -> I need to check this in detail, it might be saved in a custom field on task level

What would be the best and easiest way to achieve this, is there anything out of the box or does this need to be done with DB scripts?

Thanks
Fabio

Elio Di Puma

Hello @costifab

Unfortunately, there is currently no build in migration support for this scenario, so it needs to be done manually in the database. To synchronize the users, you need to update the IWA_User.ExternalId field for each user. This should be set to the ObjectID provided by Microsoft Entra ID. Once this is done, the user will be synchronized and their username (IWA_User.UserName) will automatically be updated to their email address from Entra ID.

My suggested approach for the migration would be:

Migrate the Engine from v8 to v12.
Stop the Engine.
Manually update the IWA_User.ExternalId for all users.

Hope this helps