arrow_back history picture_as_pdf This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ~~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 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 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 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//