Tasks and Roles: Difference between revisions

From IHRIS Wiki
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
iHRIS utiliza un mecanismo de seguridad basado en Roles y Tareas para limitar el acceso a las diversas partes del sistema. A un usuario se le asigna un rol y un rol es un conjunto de tareas que ese rol puede realizar.
iHRIS uses a task- and role-based security mechanism to limit access to various parts of the system. A user is assigned a role, and a role is a collection of tasks that the role can perform.


Este artículo describe como se definen los roles y tareas en Datos Magic y utilizados por el sistema iHRIS.  
This article describes how roles and tasks are defined in Magic Data and used by the iHRIS system.  


=Roles=
=Roles=
Un rol es una colección de [[#Tasks|tareas]] que pueden asignarse a la cuenta de un usuario.
A role is a collection of [[#Tasks|tasks]] that can be assigned to a user's account.
*los nombres de los roles se definen como los secundarios de [[Configuration (Magic) Data|ruta de magic data]] /I2CE/roles/names
*Role names are defined in [[Configuration (Magic) Data|magic data path]] /I2CE/formsData/forms/role/
*un rol $role tiene un display definido en /I2CE/roles/names/$role/display_name
*The roles are defined as entries of the role form and we need to add the last_modified value
*los roles pueden heredar tareas de otro al agregarlo como el valor de un nodo secundario de /I2CE/roles/names/$role/trickle_up <br/>Por ejemplo, en iHRIS Manage en el /I2CE/roles/names/hr_staff tenemos:
*A role $role has a $display_name defined at /I2CE/formsData/forms/role/$role/fields/name/$display_name
** display_name => HR Staff
** trickle_up => Array
*** 0 => admin
*** 1 => hr_manager
dice que el rol de hr_staff aparece como 'HR Staff' y que un hr_manager o admin tiene todas las tareas que tiene un hr_staff.


=Tareas=
For example, this XML says that the role hr_staff is displayed as 'HR Staff' and it is assignable.:
Una tarea puede ser tanto una colección de sub-tareas que tiene esta tarea y la descripción de alguna acción cuyo permiso se puede verificar. La información de las tareas se guarda en datos magic bajo /I2CE/tasks/.  Para crear una tarea se crea un nodo secundario de tipo escalar de /I2CE/tasks/task_description.  El nombre del nodo es el nombre utilizado para referenciar la tareaEl valor del nodo es la descripción de la tarea que se muestra en la página de Manejo de Tareas y RolesPor ejemplo, el nodo de magic data /I2CE/tasks/task_description puede verse así:
 
* custom_report_admin => Permite la administración del Sistema de Informes Personalizados
<configurationGroup name="roles" path="//I2CE/formsData/forms/role/">
* custom_reports_can_access => Permite acceso mínimo al Sistema de Informes Personalizados
  <configurationGroup path="hr_staff">
* custom_reports_delete => Permite eliminación de datos acerca de los informes personalizados
    <configuration name="last_modified">
* custom_reports_can_access_relationships => Permite acceso a las Relaciones de Informes Personalizados
      <value>2013-01-15 1:23:45</value>
Puede definir la sub-tarea de una tarea $task al especificar /I2CE/tasks/task_trickle_down_task.  Por ejemplo, el nodo de datos magic /I2CE/tasks/task_trickle_down/custom_reports_admin puede verse así:
    </configuration>
  <configurationGroup name="fields">
    <configuration name="name">
      <value>HR Staff</value>
    </configuration>
    <configuration name="assignable">
      <value>1</value>
    </configuration>
  </configurationGroup>
</configurationGroup>
 
=Tasks=
A task can be both a collection of sub-tasks that this task has and description of some action that can be checked for permission. Task information is stored in magic data under /I2CE/tasks/.  To create a task you create a scalar type child node of /I2CE/tasks/task_description.  That name node of the node is the name used to reference the taskThe value of the node is the description of the task displayed in the Task and Role Management pageFor example, the magic data node /I2CE/tasks/task_description may look something like:
* custom_report_admin => Allows administration of the Custom Reporting System
* custom_reports_can_access => Allows minimal access to the Custom Reporting System
* custom_reports_delete => Allows deletion of data about custom reports
* custom_reports_can_access_relationships => Allows access to the Custom Report Relationships
You can define the sub tasks of a task $task by specifying /I2CE/tasks/task_trickle_down_task.  For example, the magic data node /I2CE/tasks/task_trickle_down/custom_reports_admin may look like:
* 0 => custom_reports_can_access   
* 0 => custom_reports_can_access   
* 1 => custom_reports_delete_reports  
* 1 => custom_reports_delete_reports  
lo que dice que la tarea de 'custom_report_admin' tiene todas las tareas y derechos definidos por  'custom_reports_can_access' y 'custom_reports_delete_reports.'
which says that the 'custom_report_admin' task has all the tasks and rights defined by 'custom_reports_can_access' and 'custom_reports_delete_reports.'


Las tareas que se asignan a un rol $role son los valores de los secundarios bajo /I2CE/tasks/role_trickle_down/$role
The tasks that are assigned to a role $role are the values of the children under /I2CE/tasks/role_trickle_down/$role


Un usuario con el rol 'admin' tiene todas las tareas.
A user with the role 'admin' has all tasks.


=Usos de las Tareas y Roles=
=Uses of Tasks and Roles=
Las tareas y roles se utilizan en varios lugares:
The tasks and roles are used in several places:
*La clase principal [[Pages and Templates#Page Logic|I2CE_Page]] revisa los permisos básicos de la página.   
*The main [[Pages and Templates#Page Logic|I2CE_Page]] class checks for basic permission for the page.   
*Varias páginas revisan los roles específicos y las tareas en su método action().
*Several pages perform checks for specific roles and tasks in their action() method.
*Antes de mostrar el HTML la clase I2CE_Template, verifica que todas las tareas, roles y permisos esten satisfechos en cada nodo.
*Just before displaying the HTML the I2CE_Template, class verifies that all tasks, roles and permissions are satisfied on each node.


=Task and Role Administration=
=Task and Role Administration=
Line 40: Line 52:
For setting tasks and roles dynamically, the module 'tasks-roles' provides the page named 'roles' and the page named 'tasks' that allows creating new roles and tasks as well as defining the permission inheritance.
For setting tasks and roles dynamically, the module 'tasks-roles' provides the page named 'roles' and the page named 'tasks' that allows creating new roles and tasks as well as defining the permission inheritance.


To enable the task-roles module go to Configure Modules -> Pages -> Sub-Modules -> Tasks and Roles.


=Permisos y Analizador de Permisos=
=Permissions and the Permission Parser=
El analizador de permisos permite expresiones lógicas para combinar varios tipos de persmisos, tales como ''tarea'', ''roles'', en una ''cadena de permisos''.
The permission parser allows logical expressions to combine severals types permissions, such as ''task'', ''roles'', into a ''permission string''.


Podemos asignar tareas, roles y permisos a los nodos DOM al:
We can assign tasks, roles and permissions to DOM nodes by:
*Establecer el atributo ''rol''.  <br/>Si el valor es X, esto resulta en la cadena de permiso ''rol(X)'' que se pasa al analizador de permisos
*Setting the attribute ''role''.  <br/>If the values is X, this results in the permission string ''role(X)'' which is passed to the permission parser
*Establecer el atributo ''task''. <br/>Si el valor es X, esto resulta en la cadena de permiso  ''task(X)'' que se pasa al analizador de permisos
*Setting the attribute ''task''. <br/>If the values is X, this results in the permission string ''task(X)'' which is passed to the permission parser
*Establecer el atributo ''permiso.''
*Setting the attribute ''permission.''
Si el nodo falla cualquiera de las revisiones rol, tarea o permiso, eliminará el nodo
If the node fails any of the role, task or permission checks it will remove the node


==Tipos de Permiso: tarea y rol==
==Permission Types: task and role==
Los tipos de permisos de tarea y roles se forman rodeando el nombre de un rol con role() o el nombre de una tarea con task().  Por ejemplo, se puede crear la siguiente ''cadena de permiso'':
The task and role type permissions are formed by surrounding a role name with role() or a task name with task().  For example, you can create the following ''permission string'':
  (task(can_edit_database_list_facility_type) & task(can_edit_database_list_fav_color) || role(admin)
  (task(can_edit_database_list_facility_type) & task(can_edit_database_list_fav_color) || role(admin)
Por defecto, las tareas y roles son 'OR'ed juntos así que los siguientes son todos iguales:
By default, tasks and roles are 'OR'ed together so the following are all the same:
*task(can_edit_database_list_facility_type) or task(can_edit_database_list_fav_color)
*task(can_edit_database_list_facility_type) or task(can_edit_database_list_fav_color)
*task(can_edit_database_list_facility_type) | task(can_edit_database_list_fav_color)
*task(can_edit_database_list_facility_type) | task(can_edit_database_list_fav_color)
Line 61: Line 74:
*task(can_edit_database_list_facility_type|can_edit_database_list_fav_color)
*task(can_edit_database_list_facility_type|can_edit_database_list_fav_color)


== Tipo de Permiso: módulo==
== Permission Type: module==
Cualquier función pública de una [[Module Structure#The Module Class|clase de módulo]] puede llamarse utilizando el analizador de permisos. Por ejemplo, suponga que el modulo 'my_module' tiene un método 'my_method()' entonces podemos utilizar como la cadena de permiso con [[#Arguments|argumentos]]:
Any public function of a [[Module Structure#The Module Class|module class]] can be called by the permission parser. For example, suppose that the module 'my_module' has a method 'my_method()' then we can use as the permission string with [[#Arguments|arguments]]:
  module('my_module','my_method', [arg1], ... , [argN])
  module('my_module','my_method', [arg1], ... , [argN])
lo que resultaría en el llamado:
which would results in the call:
  $module->my_method($arg1,..,$argN)
  $module->my_method($arg1,..,$argN)
donde $module es la instancia de la clase del módulo para el módulo 'my_module.'
where $module is the instance of the module class for the module 'my_module.'


==Tipo de Permiso: formulario==
==Permission Type: form==
El módulo 'forms' incluye el tipo de formulario. La cadena de permiso con [[#Arguments|argumentos]]:
The 'forms' module adds in the form type. The permission string with [[#Arguments|arguments]]:
  form('form_name', 'form_method', [arg1] , .., [argN])
  form('form_name', 'form_method', [arg1] , .., [argN])
resulta en el llamado:
results in the call:
  $form->form_method($arg1,..,$argN)
  $form->form_method($arg1,..,$argN)
donde $form es el resultado de obtener el formulario por el nombre de 'form_name' por medio de los [[Pages and Templates#Template Data|datos de la plantilla]] para el nodo (si hubiese alguno) al que se asignó la cadena de permiso.
where $form is the result of getting the form by the name of 'form_name' via  [[Pages and Templates#Template Data|template data]] for node (if there was any) the permission string was assigned to.


==Arguments==
==Arguments==
Line 99: Line 112:
A module can add in a [[Module Structure#Fuzzy Methods|fuzzy method]] of the form ''hasPermision_$type'' to the ''I2CE_PermissionParser'' class to enable a new permission type.  For example the 'forms' module does this by adding in a new permission type 'form.'
A module can add in a [[Module Structure#Fuzzy Methods|fuzzy method]] of the form ''hasPermision_$type'' to the ''I2CE_PermissionParser'' class to enable a new permission type.  For example the 'forms' module does this by adding in a new permission type 'form.'


[[Category:Technical Overview]][[Category:Security]][[Category:Roles]][[Category:Tasks]][[Category:Review2013]][[Category:Needs Intro]]
[[Category:Developer Resources]]

Latest revision as of 21:09, 1 March 2019

iHRIS uses a task- and role-based security mechanism to limit access to various parts of the system. A user is assigned a role, and a role is a collection of tasks that the role can perform.

This article describes how roles and tasks are defined in Magic Data and used by the iHRIS system.

Roles

A role is a collection of tasks that can be assigned to a user's account.

  • Role names are defined in magic data path /I2CE/formsData/forms/role/
  • The roles are defined as entries of the role form and we need to add the last_modified value
  • A role $role has a $display_name defined at /I2CE/formsData/forms/role/$role/fields/name/$display_name

For example, this XML says that the role hr_staff is displayed as 'HR Staff' and it is assignable.:

<configurationGroup name="roles" path="//I2CE/formsData/forms/role/">
  <configurationGroup path="hr_staff">
    <configuration name="last_modified">
      <value>2013-01-15 1:23:45</value>
    </configuration>
  <configurationGroup name="fields">
    <configuration name="name">
      <value>HR Staff</value>
    </configuration>
    <configuration name="assignable">
      <value>1</value>
    </configuration>
  </configurationGroup>
</configurationGroup>

Tasks

A task can be both a collection of sub-tasks that this task has and description of some action that can be checked for permission. Task information is stored in magic data under /I2CE/tasks/. To create a task you create a scalar type child node of /I2CE/tasks/task_description. That name node of the node is the name used to reference the task. The value of the node is the description of the task displayed in the Task and Role Management page. For example, the magic data node /I2CE/tasks/task_description may look something like:

  • custom_report_admin => Allows administration of the Custom Reporting System
  • custom_reports_can_access => Allows minimal access to the Custom Reporting System
  • custom_reports_delete => Allows deletion of data about custom reports
  • custom_reports_can_access_relationships => Allows access to the Custom Report Relationships

You can define the sub tasks of a task $task by specifying /I2CE/tasks/task_trickle_down_task. For example, the magic data node /I2CE/tasks/task_trickle_down/custom_reports_admin may look like:

  • 0 => custom_reports_can_access
  • 1 => custom_reports_delete_reports

which says that the 'custom_report_admin' task has all the tasks and rights defined by 'custom_reports_can_access' and 'custom_reports_delete_reports.'

The tasks that are assigned to a role $role are the values of the children under /I2CE/tasks/role_trickle_down/$role

A user with the role 'admin' has all tasks.

Uses of Tasks and Roles

The tasks and roles are used in several places:

  • The main I2CE_Page class checks for basic permission for the page.
  • Several pages perform checks for specific roles and tasks in their action() method.
  • Just before displaying the HTML the I2CE_Template, class verifies that all tasks, roles and permissions are satisfied on each node.

Task and Role Administration

For deployment across many computers, tasks and roles should be set up in an appropriate module configuration file.

For setting tasks and roles dynamically, the module 'tasks-roles' provides the page named 'roles' and the page named 'tasks' that allows creating new roles and tasks as well as defining the permission inheritance.

To enable the task-roles module go to Configure Modules -> Pages -> Sub-Modules -> Tasks and Roles.

Permissions and the Permission Parser

The permission parser allows logical expressions to combine severals types permissions, such as task, roles, into a permission string.

We can assign tasks, roles and permissions to DOM nodes by:

  • Setting the attribute role.
    If the values is X, this results in the permission string role(X) which is passed to the permission parser
  • Setting the attribute task.
    If the values is X, this results in the permission string task(X) which is passed to the permission parser
  • Setting the attribute permission.

If the node fails any of the role, task or permission checks it will remove the node

Permission Types: task and role

The task and role type permissions are formed by surrounding a role name with role() or a task name with task(). For example, you can create the following permission string:

(task(can_edit_database_list_facility_type) & task(can_edit_database_list_fav_color) || role(admin)

By default, tasks and roles are 'OR'ed together so the following are all the same:

  • task(can_edit_database_list_facility_type) or task(can_edit_database_list_fav_color)
  • task(can_edit_database_list_facility_type) | task(can_edit_database_list_fav_color)
  • task(can_edit_database_list_facility_type) task(can_edit_database_list_fav_color)
  • task(can_edit_database_list_facility_type,can_edit_database_list_fav_color)
  • task(can_edit_database_list_facility_type can_edit_database_list_fav_color)
  • task(can_edit_database_list_facility_type|can_edit_database_list_fav_color)

Permission Type: module

Any public function of a module class can be called by the permission parser. For example, suppose that the module 'my_module' has a method 'my_method()' then we can use as the permission string with arguments:

module('my_module','my_method', [arg1], ... , [argN])

which would results in the call:

$module->my_method($arg1,..,$argN)

where $module is the instance of the module class for the module 'my_module.'

Permission Type: form

The 'forms' module adds in the form type. The permission string with arguments:

form('form_name', 'form_method', [arg1] , .., [argN])

results in the call:

$form->form_method($arg1,..,$argN)

where $form is the result of getting the form by the name of 'form_name' via template data for node (if there was any) the permission string was assigned to.

Arguments

A permission type (such as role, task, form or module) in a permission string behaves essentially like a function. Suppose that we have the general shape for a piece of a permission string:

type([arg1],[arg2],...,[argN])

Then this results in the method call:

$permissionParsrer->hasPermission_$type($node,$args)

where $node is the DOMNode the permission string was called on and $args is the array($arg1,..$argN). The permission parser turns [argM] into $argM according to the following rules:

  • if [argM] starts with a $ then it refers to template data and the following rules apply:
    • The string has the form $abcd. The value of $argM becomes the template display data with name 'abcd.'
    • The string has the form ${WXYZ}abcd. The value of $argM becomes the template data with category 'WXYZ' and with name 'abcd.'
  • <NODE> becomes the instance of DOMNode (if any) that the permission string was called on
  • <TEMPLATE> becomes the instance of I2CE_Template (if any) that the permission parser was called on
  • <USER> becomes the instance of I2CE_User that is this session
  • if [argM] starts with a single quote ' then it is a string until the next non-escaped ' is found
  • if [argM] starts with a double quote " then is is a string until the next non-escaped " is found.
    In addition the following substitution rules apply:
    • any substring starting with $ and consisting of alpha-numeric characters, - or _ is interpreted as template display data to be substituted
      For example "my name is $name" becomes "my name is Joe" if the template data named 'name' and with type DISPLAY is "Joe"
    • any substring starting with {$ is read until an enclosing } is found. The string between the ${ and } is the name of DISPLAY template data which is then substituted.
    • To prevent the above, { and $ may be escaped with a \
  • any other string of alpha-numeric characters (and a few permitted punctuation marks) is interpreted as a string

Arguments may be separated by a comma a space or a |.

New Types

A module can add in a fuzzy method of the form hasPermision_$type to the I2CE_PermissionParser class to enable a new permission type. For example the 'forms' module does this by adding in a new permission type 'form.'