Understanding the Advanced Database Editor (ADE) Table Security model

There are two levels of table security in Advanced Database Editor (ADE) to govern when you can view or modify a record of a RealTime database (RTDB) table:

1. Area of Responsibility (AOR) Security - RTDB tables that have the group field are considered AOR tables. To view a record of an AOR table, you need to:

   • Have the DNA Permission – View permission,

   • Be responsible for this Area, and

   • Ensure that the record’s group belongs to this Area.

     After you have been granted permission to view the record, the record will be displayed on an edit form (for example, Table Edit or Row Edit dialog box), and ADE will assume that you have the write access for this record (you would see that the Save button is enabled on the edit form). Then, when you perform a write operation on the record, a write command will be sent to the RealTime server. Upon receiving a write command, the RealTime server will check your set of DNA Permissions, and if you have the DNA Permission – Config_Database and/or DNA Permission – Control_SCADA permission(s) it will allow the write command to be performed. Otherwise, the write command will be rejected.

2. Table Security - This security level applies to non-AOR tables (RTDB tables without the group field), and it is configured in a special table called tableSecurity. In tableSecurity, each of the non-AOR tables are represented by a record with two values: Read Permission and Write Permission. Read Permission defines the permission you need to have to be able to write (insert, modify, delete) to a particular table/record. When you try to open an edit form (i.e., table edit or row edit) of a particular non-AOR table, ADE will get the read or write permissions of that table in the tableSecurity and compare them to your set of DNA Permissions.If you have the same DNA Permissions as the Read Permission, you will be granted read access to the table/record. If you have the same DNA Permissions as the Write Permission, you would be granted read and write access to the table/record.

   Note: When the Write Permission of a non-AOR table is empty/blank in the tableSecurity table, then ADE defaults its Write Permission to DNA Permission - Config_Database. When the Read Permission of a non-AOR table is empty/blank in the tableSecurity table, ADE does not apply any default permission to it.