Flat file CSV
Some types of systems must be registered and onboarded to Omada Identity not through a direct connection, but through an upload of flat files, representing identity and access data. Typically, such an onboarding method is used for systems where a direct connection is not allowed by the customer, or automatic provisioning is not necessary or feasible. If needed, manual or relayed provisioning to such systems can be performed.
Omada Identity supports data import from flat files only if their format and structure meet specific requirements. You can use such data, for example, in Identity Management and Access Governance scenarios.
Data from offline target systems can be imported into Omada Identity through the upload of CSV files.
Supported objects and operations
Only the full import mode is supported. The uploaded files need to contain the complete set of objects.
The object types that can be imported are:
Identity Systems
| Resource | Possible operations |
|---|---|
| Identity | Read |
| Identity owner | Read |
| Context | Read |
| Context assignment | Read |
| Context Owner | Read |
Access Systems
| Resource | Possible operations |
|---|---|
| Account | Read |
| Resource | Read |
| Resource Owner | Read |
| Resource Assignment | Read |
| Resource parent/child relationships | Read |
Ensure that the same number of files is available for each subsequent upload. When the CSV files are re-uploaded, the entire file set will be overwritten. It is not possible to overwrite them selectively.
For example, if you choose to first upload Accounts, Resources, Resource Assignments and Resource Owners, and then reupload only the first three (as they are all required), it will result in Resource Owners being missing from Omada Identity.
Minimum required permissions
None.
Implementation notes
The CSV files that you can use to upload must meet the following requirements:
- Encoded in UTF-8, ASCII, or Unicode.
- The fields must be separated by a single character. For example: comma (,) or semicolon (;).
- If a field value is NULL, this corresponds to this field being left empty.
There are no specific requirements regarding target system versions, as long as these systems support creation of appropriate CSV flat file formats.
Prerequisites
There are no specific prerequisites regarding target systems. These systems must support generation of CSV files that will be compliant with Omada Identity.
The way of creating CSV files may vary in different target systems. Depending on the target system, you may be able to generate the required files directly within the system, or you may have to use external applications to adapt the files to the needs of Omada Identity (for example, to merge the target system files if a single file does not include all the required data). One or more files of the same type (for example, multiple Identity files) can be uploaded for the same system.
When the files have been created, you can proceed either to the registration of a single system category or multiple systems within a single category.