Skip to main content
Version: Omada Identity on-premises 16.0.1

Assignments

Assignment reasons and states​

All calculated resource assignments (CRAs) have at least one reason that indicates why the assignment was created, for example, an assignment has a reason type that indicates whether the assignment was created due to a direct assignment or an assignment policy.

In addition, a reason type belongs to a state which can be either Actual or Desired:

  • Actual state assignments represent the access that an identity currently has in the connected systems.

  • Desired state assignments represent the access that companies or organizations would like an identity to have based on assignment policies and other criteria.

The following table presents an overview of reason types and states:

Actual state​

Reason typeDescription
Actual directThe assignment was added due to the existence of a direct resource assignment (DRA) in Omada Data Warehouse (ODW).
Actual indirectThe assignment was added due to the existence of an indirect resource assignment, for example, an assignment due to group-in-group in ODW.
Unconfirmed actualThe assignment was assigned because of a provisioning claim based on a Manual or Omada Provisioning Service (OPS) provisioning task.

Desired state​

Reason typeDescription
DirectThe assignment was added due to the existence of a Resource assignment data object.
The resource assignment must have one of the following statuses:
Inactive, Active, Obsolete, Disabled, Locked.
Also, if the Resource assignment has an Active, Inactive, Active, or Obsolete status, it's only considered if the time of calculation was within its validity period (plus post-validity days).
PolicyThe assignment was added due to the existence of an Assignment policy data object.
Child resourceThe assignment was added due to the assignment of an Business role (or Application role) that the resource is a child of.
Auto accountThe account assignment was added due to the identity not having an account for a system, for which the identity has a CPRA (calculated permission resource assignment), and the automatic creation of accounts has been defined for the system or a resource type.

For more details, see section Auto accounts in Accounts.
Review OKThe Review OK reason (survey result) is considered as a second-class desired state, as it is taken into consideration in a secondary cycle in Role and Policy Engine (RoPE), and will never stand alone as the only reason for an assignment. Therefore, it can be considered more as an attribute or a flag than a proper desired state. It is recommended to always use a direct assignment or an assignment policy as the desired state, and only use the Review OK reason as a temporary desired state.
AdditionalThe assignment was added by a standard or custom extension in RoPE.
info

Assignment policy scope and filters only determine whether a Policy desired-state reason is added to an assignment.

Assignments that originate from imported accounts and have an Actual Direct reason can still be calculated by RoPE even when the assignment policy conditions are not met.

As a result, such assignments may still be evaluated for provisioning actions based on their calculated and actual states.

No state​

Reason typeDescription
Implicit assignmentThe assignment of an Business role or Application role was added because the identity has assignments for all resources that are contained in the role.
Implicit childThe assignment was added due to the implicit assignment of an Business or Application role which the resource is a child of.

Additional concepts​

Implicit assignments of roles​

If an identity is assigned to all resources contained in a compound resource, for example, a business role or an application role, RoPE automatically assigns the compound resource itself to the identity with reason type Implicit assignment. It does not do so for disabled/deleted resources or for resources classified as a Permission resource.

The purposes of this are the following:

  • To be able to define Segregation of Duties (SoD) policies on the role level and have them enforced even though an identity is not directly assigned to the roles.
  • To enable access reviews where the answering persons are presented with role assignments rather than technical permissions, as the former is easier to understand from a business perspective.

Implicitly assigned compound resources are traversed by RoPE as if they were assigned in any other way. The assignments of the children get the special reason type Implicit child, instead of the Child resource.

To become implicitly assigned, a role must meet the following conditions:

  • The identity is assigned to all the child resources of the role.
  • None of the child resources is in disabled state. If any of them is in disabled state, then the role will not be implicitly assigned. However, if a child resource is marked as deleted, typically because it is deleted in the target system, RoPE will still assign the parent role implicitly if the remaining child resources are assigned.
info

The calculation of implicit assignments for new environments is disabled by default. The RoPE: Skip implicit assignments and the Skip implicit assignments for technical identities setting is set to True by default.

You can enable this functionality by setting the RoPE: Skip implicit assignments (RoPESkipImplAssns) or Skip implicit assignments for technical identities (RoPESkipImplAssnsForTechIdent) customer settings to False.

note

RoPE does not resolve implicit assignments for the unresolved identity, because in this case, the ownership of the underlying permissions is undefined, and therefore, an implicit role assignment would not reflect a well-defined state.

Revoking implicit assignments​

Implicit assignments cannot be revoked directly. Because they are derived, not explicitly assigned, there is no assignment object to remove at that level.

An assignment appears as implicit when it originates from a resource hierarchy, for example, app role - role - group. Even if the parent assignment is itself derived from further upstream assignments, the effective assignment still carries reason type Implicit assignment or Implicit child.

To remove access driven by an implicit assignment, revoke the explicit assignment at the root of the hierarchy. This removes the upstream source that generates the implicit children.

Performance considerations for implicit assignments​

When implicit assignments are enabled, RoPE loads every parent of every resource it needs for a batch before it calculates any identity in that batch. A resource that is a child of thousands of roles therefore adds thousands of resources to the batch, and RoPE discards almost all of them later in the calculation.

How RoPE loads parent resources​

RoPE loads parent resources while it prepares the batch, because the calculation cannot query the database separately for each identity:

  1. RoPE loads the resources the batch needs, such as assigned resources and policy targets.
  2. If implicit assignments are enabled, RoPE also loads all parents of those resources. This setting alone decides whether parents are loaded.
  3. RoPE links each resource to its parents, so the calculation can look them up directly.
  4. RoPE records every loaded resource, whether requested or loaded as a parent, as part of the batch.

Why RoPE needs the parent resources​

RoPE finds candidates for implicit assignments among the parents of the assigned resources. It keeps parents that are roles and have child resources, and assigns a candidate only when the identity is assigned to all of its children.

RoPE knows the full set of assigned resources only during the calculation, after it has evaluated assignment policies, additional assignments, and child resources. It must therefore load the parents of every resource that might end up assigned, not only of those that turn out to qualify.

Why resources with many parents affect performance​

The loading cost grows with the number of distinct parent resources. For a resource with many parents, RoPE has to load, cache, and link each parent. The loaded parents remain part of the batch and are processed again in later steps, for example, when RoPE calculates risk scores.

Most of this work is wasted when the parents cannot qualify. A parent role qualifies only if the identity is assigned to all of its children. For a resource shared by many roles, only the roles whose other children are also assigned can become implicit assignments.

Example

Every application role on a system has at least two child resources:

  • Its own permission, for example, Application1:Permission.
  • A shared system permission, for example, System1:Common.

The shared permission is therefore a child of every application role on that system, which can be thousands of roles. Each time the shared permission is part of a batch, RoPE loads all of these roles, although only the role of a given application permission can qualify. RoPE finds that role through its non-shared child resource anyway, so the parents loaded through the shared permission do not change the result.

In one simulation, a batch that requested 73 resources loaded about 8,000 resources. Preparing the batch took about 92 seconds, of which about 85 seconds were spent loading resources.

Impact on simulations​

RoPE loads resources the same way in regular calculations and in simulations. The impact is greater in simulations, because batches are smaller, so preparing a batch can take longer than calculating it.

Provisioning claims and validity of assignments​

A provisioning claim affects the validity of an assignment by introducing an unconfirmed actual reason for that assignment. When a provisioning task is completed and an active provisioning claim exists, the claim is treated as an actual state reason. When the assignment is recalculated, the newer actual state reason takes precedence over the older actual state reason when determining the assignment’s validity.

important: review mode

When you remain in review mode for an extended period, provisioning claims that are still in review may be purged based on the configured retention period (controlled by the Provisioning claim purging after expiry customer setting). This changes the desired state of the calculated assignment.

note

See also related concepts: