Omada.OE.Solution.OIM.Assembly Namespace

Contains a code method for populating the access request popularity statictics

Contains code methods for reassigning activities.

Running tasks of archiving data into a separate database.

Contains logic for validating attribute objects.

Validates that a new context assignment can only be created by the context owner.

When a new ContextType data object is created the class validates a number of things and modifies the form object of the referred data object type.

The ControlPolicyEvaluator validates that a control policy is not violated when a data object is saved.

When a DataSource data object is saved the class validates that the specified xml conforms to valid DataSourceML.

Contains logic for validating a delegation object

Contains logic for validating "email ownership challenge" objects. Objects of this type are used in the CIAM portal. Note that the EMAILOWNSHPCHALLENGE DOT is not always present in the system.

Hook up to the TimerController delegate EvaluateTimerEventForShadowObject. When the delegate is fired from the timer controller, the call either the RoPEEventController or the SurveyEventController depending on the shadow object type.

Contains various code methods concerning identities.

Synchronizes master data (first name, last name, job title, email and odwbusikey) from identities to their corresponding user when they are updated.

Import profile CMs for V15 or later.

When a KPI data object is saved the class validates that the specified xml conforms to valid KPIML.

Performs a count of managed identities and compares it with the license. If not complaint a license warning is added to the static license warning cache.

Contains miscellaneous code methods.

Contains code methods for "master data management" scenarios.

The Migration class contains code methods for migrating from obsolete concepts in OIM.

Contains various code methods concerning the organisational structure.

Contains logic for moving identities belonging to an org. unit being deleted.

Logic for generating random passwords for new identities.

This class can generate random passwords, which do not include ambiguous characters, such as I, l, and 1. The generated password will be made of 7-bit ASCII symbols. Every four characters will include one lower case character, one upper case character, one number, and one special symbol (such as '%') in a random order. The password will always start with an alpha-numeric character; it will not start with a special symbol (we do this because some back-end systems do not like certain special characters in the first position).

When a resource data object is updated to RESOURCESTATUS = Deleted then this handler expires all provisioning claims. We do so to avoid that provisioning tasks are generated for assignments to the resource.

Validates the integrity of resources data objects being saved.

Contains various code methods concerning role approval.

Contains various code methods concerning role assignments.

The RoleVerification class contains various code methods used for the "Verify roles" process. The 'Verify roles' process is used by system owners to verify, that an identity should still have one or more roles belonging to their system. 'Verify roles' processes are typically launched when an identity moves to another org. unit.

Contains RoPE related code methods.

Purpose of this class is to resolve human readable display values for the attributes used in the self-mgmt feature.

The code methods for shadow data objects.

Contains various code methods concerning systems.

Ensuring ODWBUSIKEY has the correct value on system data objects Note: Only on Horizon

Contains logic for validating system category objects.

Contains logic for validating system objects.

Class contains CodeMethods used in test automation

When a UIAction data object is saved the class validates that it is valid.

The set of CMs related to value generation.