~~NOTRANS~~
~~Title: Use Custom Tables and Views for Authentication~~

If you use the standard DBSecurityManager, DBWorkScreenAccess or RoleBasedDBWorkScreenAccess you have to use the following table names:

//AUTOLOGIN \\ 
USERS//

and following view names:

//V_ACCESSRULES \\ 
V_ROLESCREENS \\ 
V_USERROLES \\ 
V_USERSCREENS//

If you want to change the names without changing the source code, it's very easy to map the expected names to your own names. It's also possible to define synonyms in your database, if supported.

Simply add the following to your config.xml:

<file xml>
<application>
  …

  <databaseobjects>
    <USERS>APP_USERS</USERS>
    <AUTOLOGIN>APP_AUTOLOGIN</AUTOLOGIN>
    …
  </databaseobjects>

</application>
</file>

The mapping syntax is:

<**origtablename**>//newtablename//</**origtablename**>

It's also possible to change the column names of standard tables and views. Simply add the following to your config.xml:

<file xml>
<databaseobjects>
  <USERS_CHANGE_PASSWORD>PWD_CHANGE_FLAG</USERS_CHANGE_PASSWORD>
</databaseobjects>
</file>

The syntax for column mapping is:

<**origtablename_origcolumnname**>//newcolumnname//</**origtablename_origcolumnname**>

A hidden feature is the support for changing the YES value. The standard value for YES is Y. If you want another value, e.g., 1, simply add the following to your config.xml:

<file xml>
<databaseobjects>
  <yes_value>1</yes_value>
</databaseobjects>
</file>

The value will be used in DBWorkScreenAccess and DBSecurityManager and following tables:

//USERS \\ 
WORKSCREENS//