Terminology used in this guide
This table contains definitions for the most common security terms. For background information about security, including architecture diagrams for Infor Landmark security, see the Landmark User Setup and Security guide.
| Term | Definition |
|---|---|
| actor | A unique ID of anyone using any part of the system, including Landmark Technology. See user. |
| authentication | Authentication occurs when actors present their sign in credentials to a system. |
| authorization | The set of rules and roles that determines specific access for a system and associated data. These authorization rules and roles provide security access. For example, a user can have access to a solution to update their personal data, but cannot access other users' information. |
| context property and actor context record | A context property is a key field that the actor context record is
defined against. A context record is a filter that determines the information that is displayed. A context record is assigned to an actor to form an actor context record. When you add a new user you assign a context property value. Typically, the properties are created as part of initial system setup. |
| FSM | This guide occasionally uses the acronym FSM to refer to the Financials & Supply Management product. |
| HCM | HCM is the acronym for Human Capital Management, a product that some
customers use in conjunction with Financials & Supply Management. Note: You may see the acronym GHR in examples of
naming conventions and URLs. GHR is an acronym for Global Human
Resources, a component of HCM. Some instructions in this
document are performed using the GHR application. In those
situations, GHR is specified.
|
| roles (security roles) | A group of tasks, that is security classes, that determine what a user
can do in the system. Typically, a role is determined by the roles'
(security roles) specific tasks that a user performs to complete a
specific job. For example, the PO_Signoff role includes all security
classes that are required to sign-off on purchase orders. These
roles are assigned to the user at your site who is responsible for
that task. You can use a set of templates that contain user roles and assigned security classes. Note: In Analytics, security roles are also used.
These roles are administered through the Infor
EPM Platform Administration
console. As a best practice, use the same roles on each
system.
|
| security classes | The rules that determine user access. A rule is written against a
specific object (business class) that a user requires to perform
security classes for a specific job. Security classes are assigned
to roles and roles are assigned to users. To ensure that appropriate individuals have access in appropriate ways, classes are flexible. For example, one class can be used to give access to view a specific report. Another class can be used to give access to update data that is included in a report. The view report class is a read only class. Users who add and update data are assigned an all access class. |
| single sign on (SSO) | An authentication scheme that allows users of multiple Infor systems to sign in once for access to all products. |
| user | A user who has been assigned all required access rights and credentials to perform their tasks in an Infor solution. See actor. |