30 docs tagged with "Onboarding"

The Application onboarding process can assign System owners via Resource Assignments. This process is available in Services > Onboard application.

The Onboarded systems view contains the necessary configurations to manage an external source system from which you want to import data from, and for access systems, provision data to.

This feature enables anonymization of all or selected objects that fulfill specified criteria. It can be used to enforce the right to be forgotten as required by the EU General Data Protection Regulation (GDPR). It might be also used to anonymize sensitive data in customer databases before they are copied externally.

The Application onboarding process entails a collaboration between the Business and IT. Not all resources will require applications, and the scope of application onboarding can vary from business to business. However, there are some general guidelines on how to approach this

Omada Identity is a system that is automatically onboarded during Omada Identity installation.

This section explains how you can configure the onboard application objects. To do that, go to Set up > Administration > More > Configuration Objects.

The connectivity package export feature allows to create and export a custom connectivity package that is a representation of an already onboarded system. This package then can be used as a template for a new collector, and if available, a template for a new connector.

Follow these steps to create an application accounts and application roles manually, via forms:

This section describes the settings allowing you to configure data imports.

There are general settings that are relevant for all source systems. Connection strings and import source systems are common settings, while master data settings are specific to source systems.

Enabling the Horizons feature impacts the import and onboarding process significantly, for more information, go to Migrating to Horizons documentation.

With the Horizons feature enabled, the way import logs are stored is different. For more information, go to Import history.

During the configuration step in application onboarding, you will have to create several objects. It is best to agree on a stringent naming standard from the beginning, so that it can be used on all the applications consistently.

This advanced configuration section provides information that enables you to set up Omada Identity Data Warehouse (ODW) to suit your company’s business needs.

You perform all configuration of Omada Provisioning Service (OPS) in Enterprise Server. Make sure that you have installed the Enterprise Server Integration feature as part of the OPS installation on the server that hosts Enterprise Server.

Import of data from target systems can be started from the Omada Identity Portal. There are two ways this can be done, through a WMI call to the SSIS Server (default), or by creating and starting SQL Agent jobs. Regardless of the chosen alternative, you must complete a number of security operations on the SSIS Server.

This section describes the settings allowing you to configure provisioning. Provisioning can be enabled for systems containing Access Rights, Identity data or both.

Here you will find different settings to define resource, resource types, and resource folders.

This section provides detailed information on configuration and use of the SSIS Packages for Omada Identity Data Warehouse.

First step includes creating an application

Next step includes configuring an application using the Application onboarding process. To do so, follow these steps:

Next in the process, you must create an account for the application, that is, the built-in application account used for new resources. To do so, follow these steps:

The newly created application resources are enriched with business descriptions and other relevant attributes.

In this final step, the approver can review the resources created by the business owner and make edits if required. There is also the option of returning it to the previous step. By default, this activity is assigned to the creator of the application, but this can be configured to be, for example, an onboarding administrator group. A task will appear for the creator of the application, that is, the IT Owner.

This section describes the settings allowing you to define onboarded systems.

To specify the settings that are related to the individual task, click the task to open a dialog box in which you must configure various types of settings.

This chapter lists tasks, settings and procedures that are valid for all types of onboarded system categories. You will find information about:

This section provides information on the use and configuration of the import and provisioning thresholds.

The Transfer ownership survey is used to transfer ownerships of objects when an identity is leaving the organization.

If your external system uses a vault provider to store sensitive credentials, you can use the Vault Service when onboarding a system. This allows you to retrieve credentials from an external vault rather than from local storage.