# Migration Ignition 8.1 to 8.3 User Sources **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [July 9, 2026, 9:41pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342 "2026-07-09T21:41:42Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![adrian.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@adrian.hernandez](https://forum.inductiveautomation.com/u/adrian.hernandez)\ **Post date:** [July 9, 2026, 9:41pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/1 "2026-07-09T21:41:42Z")
Hi, I'm trying to migrate an installation of Ignition 7.9 to Ignition 8.3, when I migrate first to 8.1 everything looks good, but when I try to migrate to 8.3 It didn't work specifically in the login. The original application have a User Sources in MYSQL database and It is configure in Manual Mode. I don't know if in Ignition 8.3 this options did't works. ---
**Author:** ![Nathan\_Wright](https://avatars.discourse-cdn.com/v4/letter/n/ed8c4c/32.png) [@Nathan\_Wright](https://forum.inductiveautomation.com/u/Nathan_Wright)\ **Post date:** [July 10, 2026, 6:10am UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/2 "2026-07-10T06:10:51Z")
I believe the Database Authentication User Source remains unchanged in 8.3. It would be beneficial to reset the password on the 8.3 gateway and manually investigate why the new user source is not functioning correctly, if you haven't already. [Gateway Command-line Utility - gwcmd | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/gateway/gateway-command-line-utility-gwcmd#gateway-password-reset) The 8.3 upgrade guide does mention changes to gateway security, with some settings not porting over from 8.1 and requiring manual intervention. > **[Gateway Security​ - 8.1 to 8.3 Upgrade Guide | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/getting-started/installing-and-upgrading/ignition-8-upgrade-guide/81to83-upgrade-guide#gateway-security)** > > 💡Have feedback for this page? Let us know on the IA Forum. | Overview ---
**Author:** ![adrian.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@adrian.hernandez](https://forum.inductiveautomation.com/u/adrian.hernandez)\ **Post date:** [July 10, 2026, 5:36pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/3 "2026-07-10T17:36:34Z")
The problem is when I try to open an application in vision module, it's appears don't take the security. But when I test it from the Identity Provider, it works. ---
**Author:** ![Sfenwick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sfenwick/32/82355_2.png) [@Sfenwick](https://forum.inductiveautomation.com/u/Sfenwick)\ **Post date:** [July 10, 2026, 6:15pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/4 "2026-07-10T18:15:12Z")
I'm guessing you upgraded from 7.9 \> 8.1 \> 8.3, is that correct? Are you on the most recent version of 8.3? When it fails, do you see anything in the gateway logs or the wrapper.log file afterwards? ---
**Author:** ![adrian.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@adrian.hernandez](https://forum.inductiveautomation.com/u/adrian.hernandez)\ **Post date:** [July 13, 2026, 2:39pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/5 "2026-07-13T14:39:53Z")
Yeah, I upgrade from 7.9 \> 8.1 \> 8.3, In the version 8.1 the login works well, but the problem is in the version 8.3 only in a vision proyect that use a especific data base for the security, the wrapper.log don't show anyting only the pop up show this error: GatewayException: Cannot invoke "com.inductiveautomation.ignition.common.gson.JsonPrimitive.getAsString()" because the return value of "com.inductiveautomation.ignition.common.gson.JsonObject.getAsJsonPrimitive(String)" is null caused by NullPointerException: Cannot invoke "com.inductiveautomation.ignition.common.gson.JsonPrimitive.getAsString()" because the return value of "com.inductiveautomation.ignition.common.gson.JsonObject.getAsJsonPrimitive(String)" is null Ignition v8.3.7 (b2026060908) Java: Azul Systems, Inc. 17.0.18 ---
**Author:** ![Sfenwick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sfenwick/32/82355_2.png) [@Sfenwick](https://forum.inductiveautomation.com/u/Sfenwick)\ **Post date:** [July 13, 2026, 3:08pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/6 "2026-07-13T15:08:17Z")
I suspected so but wanted to double check. I'd suggest contacting our support department and getting a ticket made. That NullPointerException sounds like a bug that we didn't expect or anticipate. [Support](https://support.inductiveautomation.com/hc/en-us) ---
**Author:** ![adrian.hernandez](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@adrian.hernandez](https://forum.inductiveautomation.com/u/adrian.hernandez)\ **Post date:** [July 13, 2026, 4:11pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/7 "2026-07-13T16:11:27Z")
I found the problem, In the table of the users It has a column with the phone contact and this user has this column in NULL, when I replace this null with empty string It´s work. But I don´t know why the last version of Ignition v8.3.7 has this error. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 13, 2026, 4:12pm UTC](https://forum.inductiveautomation.com/t/migration-ignition-8-1-to-8-3-user-sources/116342/8 "2026-07-13T16:12:38Z")
This is just a bug on our end; we're not being sufficiently defensive about a property value possibly being null. Even though you've worked around it, a report to support would help us get it logged and fixed for the next time.