We have identified incorrect behavior in Ignition Version 7.2.9 using a database authorization profile with an Oracle database.
Ignition is not using our custom column names. For example, we have a password column name of “PW” defined on the users table, but Ignition errors out on attempted authentication with an oracle error on column “Password”. The system then autocreates an additional column called “Password”, but then gives an error that it cannot find the column “PASSWORD”. This is due to the case sensitivity of Oracle.
So basically, the problem is twofold. We cannot use custom column names, and the default values do not work in Oracle.