Authorization Tables

Previous Next

See Also

All application definitions required for authorization are stored in three authorization tables:






These tables are populated (filled) with the definitions they require for a particular application using the Fill Authorizer Tables option from the Authorizer Tools menu. These definitions include the names of tables and columns associated with the application, together with their most important properties. The definitions are taken either from the repository where the application is being developed or from the flat file (CON) from which the application is being run.

Once the authorization tables have been populated for an application, all authorization tasks associated with the application can then be performed using the Authorizer, and the rules stored in the tables. User groups can thus be defined with access rights to individual columns and tables within the application.

This feature could be especially useful in the USoft application development environment, where authorization can be specified for USoft Developer's Definer. You can restrict access to specific areas of the Definer at user group level. For example, you could decide that only members of a certain user group should be allowed to modify tables in the applications that are being developed with the Definer. This restriction can be enforced using the Authorizer.


If you make changes to your data model, you must re-populate the authorization tables for the application in question. Note that you may also have to make changes to the authorization specification using the Authorizer to take account of changes to tables and columns used by the application.