[Testing Environment – DB p. 1] Authorization

I’m going to use this DB entry article to introduce notation I’m going to incorporate In following articles. First of all I put in charge READIBILITY – as more important in those rather learning materials, than any common (or custom) notation or standard.

First of all – table naming conventions:
• Names are simple, singular words, separated with underscore, describing the content or entity
• Tables containing dictionary data start with prefix "dic_"

I’m not designing there multilingual support (but I left this an open issue – I use dictionary tables whenever translatable data appears, so one can easily add translations table for them if necessary) or care for all fields that might be useful – I’m going to incorporate as few fields only when they are needed or excused by current article. I also do not care now schemas, ownership or complicated indexes (well I put them in place, but I will not mark them on diagrams or discuss this area).

System is being designed in the way that can be used both by stationary users, offshore ones as well with closed and public beta testers. Therefore a set of permissions is going to be implemented. System is also designed to support many games (as well generally other IT projects) and allow access one parson to many games. Here it goes basic DB schema:



Some notes about tables and fields:

• Game – main table, now just containing game identifier and simple name.
• User – table containing users, fields are obvious, but one might require additional comment – it’s display_name, that is going to be used on forums, lists etc. Generally it shall be name + surname, but is intended to be unique (but for security reasons different than login).
• Dic_user_role – intended to contain main role that user has in given game. It does not grants any permissions – it’s rather used as sub header on forum, discussions, logs etc.
• Dic_access_permission – defines available permissions to the system
• Assigned_access_permission – lists permissions that has been granted for specific game access. Field value might be used by some permissions, but we do not use it yet.
• Game_access – defines user has access to specific game (with dates) at particular role with set of granted permissions.

There might be defined specific default template of permissions depending of assigned role to just assist in creation of user access. This might be stored in db or be defined only on backend application. Administrator shall have full possibility to limit or extend that list for particular user.