Documentation

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
applications:custom_tableauth [2018/02/07 08:09]
admin
applications:custom_tableauth [2020/07/03 14:01]
cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation)
Line 1: Line 1:
 ~~NOTRANS~~ ~~NOTRANS~~
-~~Title: Use custom tables ​and views for authentication~~+~~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: If you use the standard DBSecurityManager,​ DBWorkScreenAccess or RoleBasedDBWorkScreenAccess you have to use the following table names:
Line 47: Line 47:
 <​**origtablename_origcolumnname**>//​newcolumnname//</​**origtablename_origcolumnname**>​ <​**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:+A hidden feature is the support for changing the YES value. The standard value for YES is Y. If you want another valuee.g.1, simply add following to your config.xml:
  
 <file xml> <file xml>
Line 57: Line 57:
 The value will be used in DBWorkScreenAccess and DBSecurityManager and following tables: The value will be used in DBWorkScreenAccess and DBSecurityManager and following tables:
  
-//USERS+//​USERS ​\\ 
 WORKSCREENS//​ WORKSCREENS//​
  
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information