Security Model

Languages:

English| | Translate this article...

Back to Main Page

Security Model

This page describes how different InfiniteERP security concepts influence development.

InfiniteERP's security concept consists of three main parts:

• Multi-Client/Multi-organization: defines which client/organizations are visible to a user and referenceable from other client/organizations.
• Data access level (of a table): defines the client/organization which is allowed for data stored in a specific table. See the access level field of AD_Table.
• Access definition: InfiniteERP has several access definitions, allowing for fine-grained access control, see the tables in the org.openbravo.model.ad.access package.

This section discusses security and access definitions from the perspective of a developer. Where necessary references to functional documentation are used.

The developer can work in two modes in InfiniteERP:

1. Traditional: using sqlc, etc. 2. Data Access Layer: using the Data Access Layer.

Both approaches are discussed separately.

Security concepts and InfiniteERP Servlets

The tables in the org.openbravo.model.ad.access package define access control for windows/tabs, processes, workflow, etc.

The security checks using this table are implemented by the HttpSecureAppServlet servlet. Any servlet extending this class will automatically inherit this security implementation.

Security concepts and XSQL and Manual Code

InfiniteERP provides a standard way to extend SQL queries with filters for accessible clients and organizations. This is discussed in detail in this section of the developer's guide:

• XSQL Definition
• XSQL Java Usage

Security concepts and the Data Access Layer

For the developer the Data Access Layer provides several interfaces (OBCriteria and OBQuery) that take automatic care of specific security aspects:

• filter for readable clients/organizations
• filter for readable tables (based on AD_Window_Access)

In addition, checks are done when retrieving a value of a property. The data access layer makes a distinction between the following two read-modes (on object level):

• direct readable: all properties of the object are readable; this readability is defined by the AD_Window_Access table
• derived readable: only the id and identifier properties are readable; derived readable entities are entities which are not directly readable but are referred to by directly readable entities

The DAL also checks write access when changing properties of a business object. Write access is also checked when an object is saved to the database. The following checks are done:

• the user has write access to the client/organization
• the user has write access to the table of the object (defined in the AD_Window_Access table)
• the client/organization of the object fit to the access level of the table
• the object only refers to other objects which are in the natural tree of organizations of the object itself

The data access layer also performs specific authorization checks when an object is deleted: the user must have access to the object and it must be deletable.

Application Administrators

There is an administrator flag on the Role window that enables users to make configurations at different levels depending on their role.

There are 4 different levels in InfiniteERP:

System level

• There is no flag for System level.
• Users logged as System Administrator are able to configure settings at System level.
• These settings will be available to everyone.

Client level

• There is a Client Administrator flag on the Role tab.
• Users are able to configure settings at Client level if the logged role has the flag enabled.
• These settings are available to all the users on the role's client.

Organization level

• There is an Organization Administrator flag on the Org Access tab.
• Users are able to configure settings at Organization level on all the organizations of the logged role that have the flag enabled.
• These settings are available to all the users logged on that Organization.

Role level

• There is a Role Administrator flag on the User Assignment tab.
• Users are able to configure settings at Role level on all the roles it is assigned to with the flag enabled.
• These settings are available to all the users logged with that role.

Upgrading from previous versions

When a role is created manually all the flags are set to false by default. There is a module script defined to set as true the flags based on the following rules:

Client Administrator

• All roles with access to (*) organization and to the Initial Organization Setup form.

Organization Administrator

• All the assigned organizations of a role with access to the Initial Organization Setup form.

Role Administrator

• All the roles assigned to a user if at least one of the roles has access to the Role window.

Notice that this module script only populates the flags the first time these flags are added. On the following core updates, the flags won't be updated and the configuration has to be done manually.

Roles created by the Initial Client and Organization setup

The Initial Client and Organization Setup forms automatically create some users and roles. These ones have the flag initialized to true.

Initial Client Setup

• The role created has the Client Administrator flag set to true.
• The user created has the new role assigned with the Role Administrator set to true.

Initial Organization Setup

• The role and the organization created have the Organization Administrator flag set to true.
• The user created has the new role assigned with the Role Administrator set to true.

See Also

• Data Access Layer
• Application Dictionary
• Multi Client and Multi Org

References

• Security Model — Etendo Documentation

---

This page is a derivative of Security Model by Openbravo Wiki, used under CC BY-SA 2.5 ES. This work is licensed under CC BY-SA 2.5.