|
Powered by STFWorks© |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The
Easy Entra Integration™ is an automated seamless way to keep your Oracle
Fusion Applications user accounts synchronized with your Microsoft Azure
Entra (Active Directory) service. Once enabled, you can control the
synchronization of Employee Names, Phone Numbers, Addresses, Emails,
Organization Information, Job Titles and more. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Getting Started Organizing the setup of the integration takes careful
planning. You will need the following information:
See the Preparing Connections (below) section for detailed instructions. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Step 1: Register When you log into the Easy Entra Integration administration site for the first time, you will be asked to provide contact information.
When you save the information, you will receive a confirmation. You will also note there are additional configuration items available for Matching, Mapping, Entra Connection and Fusion Connection.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Step 2: Fusion Connection Configure the Fusion connection by selecting the Fusion Env tab.
Save the connection. Use the Validate button to verify a successful connection.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Step 3: Azure Entra (AD)
Connection Configure the Fusion connection by selecting the Entra Env tab.
Save the connection. Use the Validate button to verify a successful connection.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Complete At this point, the core setup is complete. In the next four sections we will explore the configuration options available. · Matching Rules · Data Mapping · Synchronization Schedule · Administrative Users |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Powered by STFWorks© |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Matching Rules For the Easy Entra Integration to work efficiently, it must be able to match Fusion User accounts with Azure Entra accounts. The matching tab in the configuration console enables you to establish rules for this.
The integration will utilize two of the Azure Entra Extended Attributes to hold the Fusion Person ID and Person Number values. You have the option to choose which of the available Fifteen (15) extension attributes are to be used for this. Additionally, you have the ability to assign up to 5 additional matching rules. When the integration is attempting to match accounts, any single rule where the Azure Entra value equals the Oracle Fusion value is required to establish a match. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Data Mappings The Easy Entra Integration maps fields between Azure Entra and Oracle Fusion based upon the mapping you defined. You have the ability to specify which of the two systems is the “owner” of the data, thereby indicating which system establishes the enterprise value and which system is synced to match that enterprise value. The default map establishes Oracle Fusion as the “owner” of account enablement, nickname, employee name, display name, work and mobile phones, email address, home address, organization and job titles. The system enables you to change the ownership of employee name, work and mobile phones, email address and home address.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Synchronization Schedule The Easy Entra Integration enables you to periodically run the synchronization process on two possible schedules, “Every X Period”, and “Specific Time”. Enabling a schedule is optional, however, without at least one, the synchronization process will have to be launched manually. Only a schedule where the Enabled checkbox is checked will be active in. The “Every X Period” schedule will run every X period (minutes, hours, days). So, for example, setting this schedule with
Will result in the integration running every 2 hours.
The “Specific Time” schedule will run at a specified day and time. So, for example, setting this schedule with
Will result in the integration running every Day at 1:30am. (Note: The schedules are time zone aware, so this schedule will run at 1:30am according to the time zone selected).
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Administrative User
Accounts The Easy
Entra Integration is designed to allow additional administrators access to
the configuration. This can be done on the User Accounts tab. Quickly and
easily add, disable and delete user access accounts.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Execution History You have the ability to monitor and review historical synchronization executions of the Easy Entra Integration on the History tab.
Easily search history with the filter conditions and review the run results.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Powered by STFWorks© |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Creating an account in
Oracle Fusion
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Powered by STFWorks© |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Registering an Application
in Azure Entra (AD) The
Easy Entra Integration requires access to Azure Entra (AD) with a certain amount of administrative privileges. The integration is able to create and disable accounts as well as update
account profile information, which requires certain roles.
Registering
Access to the Azure Entra There are two options for granting access to your Azure Entra system: 1. Named User: In this configuration, the integration will run as this user 2. Certificate: In this configuration, the integration will run as a background process
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Powered by STFWorks© |