• CSV Flat file located in Oracle Cloud Infrastructure (OCI) Object Storage in your tenancy

Flat File orchestrated system supports the following modes:

• Authoritative Source
• Managed System

The Flat File orchestrated system supports the following operations:

• Create Account
• Delete Account
• Add Entitlement
• Remove Entitlement

• Create a compartment, accessgovernance/
• Create a local identity user, agcs_user in any domain in your tenancy.
• Create an identity group, agcs_flatfilegroup in any domain in your tenancy.
• Assign the identity user agcs_user to the identity group agcs_flatfilegroup.
• Create a policy, agcs_flatfilepolicy, with the following policy statement:

  allow group <groupname> to manage objects in compartment <compartmentname>
      where target.bucket.name = 'bucketname'

  For example:

  allow group agcs_flatfilegroup to manage objects in compartment accessgovernance
      where target.bucket.name = 'bucket-20231130-1143'

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:

1. From the Oracle Access Governance navigation menu icon , select Service Administration → Orchestrated Systems.
2. Click the Add an orchestrated system button to start the workflow.

On the Enter Details step of the workflow, enter the details for the orchestrated system:

1. Enter a name for the system you want to connect to in the What do you want to call this system? field.
2. Enter a description for the system in the How do you want to describe this system? field.
3. Determine if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following checkboxes.
   • This is the authoritative source for my identities
   • I want to manage permissions for this system
   The default value in each case is Selected.
4. Click Next.

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources. To add owners:

1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.

You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

On the Account settings step of the workflow, enter details of how you would like to manage accounts with Oracle Access Governance when configured as a managed system:

1. Select where to send notification emails when an account is created. The default setting is User. You can select one, both, or none of these options. If you select no options then notifications will not be sent when an account is created.

   • User
   • User manager
2. When an identity moves within your enterprise, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. In some cases the identity will no longer require certain accounts which are not relevant to their new role in the enterprise. You can select what to do with the account when this happens. Select one of the following options:
   • Disable
   • Delete
3. When an identity leaves your enterprise you should remove access to their accounts. You can select what to do with the account when this happens. Select one of the following options:
   • Disable
   • Delete

Finally, you are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:

• Customize before enabling the system for data loads
• Activate and prepare the data load with the provided defaults

<ServiceInstanceName>/<OrchestratedSystemName>
    failed
    inbox
    outbox
    sample
    schema

These folders fulfill the following purposes:

• failed: Files with any kind of data issue will be moved to this folder under the respective entity folder, in the event of a dataload operation failure.
• inbox: Contains the entity subfolders in which CSV files should be placed to be included in the dataload operation.
• outbox: Used to output the provisioning events for each entity.
• sample: Contains example CSVs with the expected header. These can be used as a reference for generating data and putting in the inbox for data load. These files should not be altered.
• schema: contains the JSON representation of each entity's schema.This can be referred to for understanding details like:
  • dataType
  • Mandatory attributes
  • Whether an attribute is multivalued or not
  • If the attribute is complex and has nested attributes (dataType will be CUSTOM)
  • Supported dataTypes are:
    • TEXT
    • NUMBER
    • DECIMAL_NUMBER
    • DATE
    • FLAG
    • CUSTOM

Custom attribute names should meet the following requirements:

• start with a character: A-Z or a-z
• contain only characters or numbers: A-Z or a-z or 0-9
• For the DATE type attribute, only long value is supported
• Custom attributes can only be added, they cannot be deleted
• A custom attribute of CUSTOM type cannot be added