# Authentication Profiles against Oracle

**URL:** <https://forum.inductiveautomation.com/t/authentication-profiles-against-oracle/3912>\
**Category:** Ignition\
**Created:** [January 25, 2012, 9:07pm UTC](https://forum.inductiveautomation.com/t/authentication-profiles-against-oracle/3912 "2012-01-25T21:07:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryanbeno](https://avatars.discourse-cdn.com/v4/letter/r/8baadc/32.png) [@ryanbeno](https://forum.inductiveautomation.com/u/ryanbeno)\
**Post date:** [January 25, 2012, 9:07pm UTC](https://forum.inductiveautomation.com/t/authentication-profiles-against-oracle/3912/1 "2012-01-25T21:07:38Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [February 9, 2012, 6:16pm UTC](https://forum.inductiveautomation.com/t/authentication-profiles-against-oracle/3912/2 "2012-02-09T18:16:09Z")

</div>

You don’t have the “Expert Configuration” mode enabled by any chance, do you?