Security

PermeAgility has integrated security which allows you to configure users and give them access to various functions available in the application.  

While many application servers manage security at the application level and use a common database login user for all database access, PermeAgility security is integrated with the database security to ensure security and still allow users to also access the database using other tools.  All user sessions have their own unique pool of connections logged into the database using the user's database login userid. Because of this architecture, even though a user can access a service, rights must also be granted to tables that the service needs.  For information on how to grant users rights to tables, see Table management.

All of the security configuration for services is managed in tables in the database.  It is not recommended that you give any users other than the system administrator access to these tables.  These tables serve the following purposes:

• • OUser - OrientDB table defines a user in the system. A user can have many roles

  • ORole - OrientDB table defines a functional role for the system.  Many users can belong to a role and many functions can be made available to a role.

  • Menu Item (menuItem) - Every service available to a user must have a record in this table. Many records in this table are usually also used in a menu to enable the function to appear on the menu when the user has access to it.

  • Menu - This table configures menus, menus apply to all users but only items available to the user will be shown.  Make the menu table ORestricted to have role based menus.

Use the tables service to add and maintain users, roles, keys and the tables that link them.  For more information on how to edit data in tables, see Schema management.

For more information about OrientDB security see the OrientDB security documentation