But I see in “What’s new in 2024.1” that there is a new standard feature:
User Account Security Maintenance now has the Allow API V1 check box. This permission indicates whether the user can run the original Kinetic version 1 application program interfaces (APIs). Existing users automatically have this permission. However by default, new users do not have this permission.
Since this is now the default setting, I guess that removing this permission would probably work for users in an installation that has never been on a version prior to Kinetic (like mine). Are there any common features or integrations that would be incompatible with this setting?
Just found out the Epicor Data Discovery does not work if you disable APIv1.
I mean EDD, hardly ever works anyway, but this prevents access for any user without APIv1 enabled.
So far, turning off API V1 hasn’t caused us problems (Kinetic in the browser works fine), however we are still in the implementation phase and probably have not finished testing everything yet.
In June EpicCare did confirm for me that the online documentation is incorrect: they had originally planned to begin disabling V1 by default for newly created users in 2024.1 (as the documentation says), but decided to delay that change until 2024.2.
I said no, because almost all of the web UI for Kinetic uses API v1, so if it was really disabled, it shouldn’t, but there is some Tom Foolery for the application itself that still allows it to work.
