Solution concepts
This chapter describes Omada Identity solution concepts that are important to understand in the context of this document.
Conceptual Data Model
The diagram shows the main concepts that are in scope in Omada Identity as well as how the concepts are related.
For definitions and explanations of the above concepts and abbreviations, see the Glossary.
Identity status
The diagram and table show the standard identity statuses and their transitions in Omada Identity:
Role and Policy Engine (RoPE) disables an identity's account assignments if its status is Pending, Terminated, Disabled, or Locked. Role and permission assignments are not affected. For details, see How RoPE uses the identity status.
The IDENTITYSTATUS property supports a fixed set of values. Do not add custom values, as they are unsupported and may cause unintended behavior in the solution.
| Status | Description |
|---|---|
| Active | The identity is active. This is the normal status for an identity (employee). |
| Disabled | A manual status that the standard status event definitions do not set or change. Use it to suspend an identity outside the normal lifecycle, for example, while a pre-employment check is pending. |
| Inactive | The identity is onboarded or otherwise approved; however, its validity period has not yet been reached. An event sets the status to Active when the validity period is reached for the identity. |
| Locked | The identity has been locked for security reasons, for example, due to the suspicion of a security breach. |
| Pending | The identity has been requested but not yet approved, for example, a new contractor. This is a manual status, like Disabled. When the identity is approved, its status changes to Inactive, Active, or Terminated, depending on its validity period. |
| Terminated | An event definition sets the status to Terminated after the Valid to date has passed. |
Automated status transitions
Three standard event definitions update identity statuses. They are all triggered by the Update object status timer, which runs every 15 minutes.
| Event definition | Sets status to | Applies to identities where |
|---|---|---|
| Update identity status (inactive) | Inactive | Valid from is later than the current date and time, and the status is Active or Terminated. |
| Update identity status (active) | Active | Valid from is not later than the current date and time, Valid to is not earlier than the current date and time, and the status is Inactive or Terminated. |
| Update identity status (terminated) | Terminated | Valid to is at least one day earlier than the current date and time, and the status is Inactive or Active. |
Identities with the status Pending, Disabled, or Locked are never changed automatically. The third event definition sets the status to Terminated only after the Valid to date has passed by at least one day. Whether the identity still has access on the Valid to date itself depends on the extendValidityPeriods setting. For details, see Time zones.
Timing: A status change may lag behind the relevant date by up to one timer interval. It can take longer when many identities are affected, because each event definition handles at most 10 identities per run by default (Maximum number of objects handled). This does not delay access changes: RoPE evaluates assignments against the validity period, not the identity status.
These event definitions are part of the standard solution but can be modified. If they have been changed, the transitions described above may no longer apply.
Resource Status
The diagram and table below show the standard resource statuses and their transitions in Omada Identity.
The resource status is not synchronized from the target systems.
| Status | Description |
|---|---|
| Active | The resource is active. This is normal state of a resource. The Active status is updated by automated event when the Valid from date is reached. |
| Disabled | A manual status that is not set by default. RoPE disables all assignments to the resource. |
| Inactive | The resource's Valid from date has not been reached. |
| Obsolete | The resource's Valid to date has passed. |
| Deleted | The resource is set to Deleted during an import when it is no longer available in the target system. |
RoPE disables assignments only when the resource status is Disabled or Deleted. Inactive and Obsolete do not disable assignments by themselves; RoPE uses the resource's Valid from and Valid to dates instead. After Valid to, assignments are disabled during the resource type's post-validity period and then removed.
Resource Assignment Status
The diagram and table show the standard Resource Assignment statuses and their transitions in Omada Identity:
| Status | Description |
|---|---|
| Active | The resource assignment is active. This is the normal status of the assignment after approval and within validity. |
| Disabled | This is a manual status and not reached by default. If applicable, all related calculated assignments are also disabled. |
| Inactive | The assignment is valid; however, the Valid from date has not been reached. |
| Locked | This is a manual status and not reached by default. If applicable, all related calculated assignments are disabled. |
| Obsolete | The Valid to date of the direct assignment is reached. |
| Pending | The direct assignment was requested using the access request process and has a pending approval. The direct assignment uses the standard access request process - an identity requests access, the request is approved, then a resource assignment is created that is associated with identities. |
| Rejected | The direct assignment was rejected in the Approval of access requests process. |
| Cancelled | The resource assignment has been cancelled because the user cancelled an access request. |
Assignments are considered Disabled if the resource assignment status is Disabled, Locked, or Obsolete.
Role and Policy
Identity Calculation Trigger
Each RoPE calculation cycle has two phases:
- Phase one is event-based queuing.
- Phase two is identity processing.
During the event-based queuing, RoPE checks all events in the Desired state data (Omada Identity) and in the Actual state data. Then, RoPE flags the identity for calculation.
The potential calculation events in Omada Identity are:
- Creation,
- Resources,
- Context assignments,
- Delegations,
- Modification,
- Resource assignments,
- Assignment policies,
- Expiration of identities,
- Contexts,
- Constraints.
In the Omada Identity Data Warehouse (ODW) account, the potential calculation events are Resources and Resource Assignments.
Birth right provisioning
When identities are onboarded, basic entitlements or roles (birth rights) are assigned to them. These roles are updated in case of organizational changes, and then removed when employment is terminated.
Account types
In Omada Identity, all account resources have an account type. Account types should be kept to a few logical and meaningful types to ensure a well-functioning solution when using roles. However, oone important reason for having more than one account type is to separate the privileged access from the personal account.
A Personal account is the default/primary account for employees and contractors.
A Privileged account enables elevated access.
The following diagram shows how resources are assigned:
The following diagram demonstrates how resources are assigned when business roles are used:
All resource objects are defined for one or more account types.
A resource (permission or role) can only be assigned to an account type that it's defined for. To use an account type in a system, you need a corresponding Account resource. Account resources can only be defined for a single account type. Permissions can be defined for multiple account types. Roles should only be defined for a single account type to avoid increased complexity for the end-user. Child permissions are only assigned to accounts of the account type of the role.
When you define an assignment policy, you should specify that it only applies to accounts of specific account types. We recommend that you only include one account type per assignment policy to avoid increased complexity.
The Microsoft tier model
Some organizations use the Microsoft tier model to mitigate unauthorized privilege escalation. Without it, there would be multiple privileged account types, for example:
- Personal – Default/primary account for employees and contractors
- Privileged Tier0 – Account that enables elevated access
- Privileged Tier1 – Account that enables elevated access
- Privileged Tier2 – Account that enables elevated access
The diagram shows the assignment of privileged access:
For more details, see the information provided by Microsoft: Securing privileged access Enterprise access model | Microsoft Learn.
Account type model
The account type model prescribes that an identity can only have one account in a system of a specific account type.
The account type model only applies to ordinary (human) identities, and does not apply to Technical identities or the special Unresolved identity, as they are allowed to have more than one account of the same type in the same system.
Technical identities are used to bundle accounts and access rights that are used by a specific system or application. A Technical identity has an owner who is always an ordinary (human) identity.
The Unresolved identity is assigned by Omada Identity as owner of all accounts for which an actual owner cannot be determined.
Account type policies
In the ODW, the account type for accounts can be set by an account type policy or by a custom join extension. (A custom join extension is a custom SSIS package that can perform advanced join logic.)
Account type policies are set per source system. For more information, refer to Import and onboarding.
If an account type is present in a connected system or created in an account type policy but does not exist in Omada Identity, then it's automatically created when data is exported from ODW to Omada Identity.
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 shows an overview of reason types and states: