4 Configuring the Workday Connector for an Authoritative Application
You must configure connection-related parameters that the connector uses to connect Oracle Identity Governance with your target system and perform connector operations. In addition, you can view and edit mappings between reconciliation fields in Oracle Identity Governance and target system columns, predefined correlation rules, situations and responses, and reconciliation jobs.
4.1 Basic Configuration Parameters for the Workday Authoritative Connector
These are the connection-related parameters that Oracle Identity Governance requires to connect to your target system. These parameters are applicable for authoritative applications only.
Table 4-1 Parameters in the Basic Configuration Section for the Workday Authoritative Connector
Parameter | Mandatory? | Description |
---|---|---|
hostName |
Yes |
Enter the Workday host name. Sample value: |
Password |
Yes |
Enter the password for the user name of the target system account to be used for connector operations. |
tenant |
Yes |
Enter the Workday tenant ID. Sample value: |
username |
Yes |
Enter the user name of the target system that you create for performing connector operations. Sample value: |
Connector Server Name |
No |
By default, this field is blank. If you are using this connector with the Java Connector Server, then provide the name of Connector Server IT Resource here. |
proxyHost |
No |
Enter the name of the proxy host used to connect to an external target. Sample value:
|
proxyPassword |
No |
Enter the password of the proxy user ID of the target system user account that Oracle Identity Governance uses to connect to the target system. |
proxyPort |
No |
Enter the proxy port number. Sample value:
|
proxyUser |
No |
Enter the proxy user name of the target system user account that Oracle Identity Governance uses to connect to the target system. |
4.2 Advanced Setting Parameters for the Workday Authoritative Connector
These are the configuration-related entries that the connector uses during reconciliation and provisioning operations.
Table 4-2 Advanced Setting Parameters for the Workday Authoritative Connector
Parameter | Mandatory? | Description |
---|---|---|
Bundle Version |
Yes |
This parameter holds the version of the connector bundle class. Default Value: 12.3.0 |
Connector Name |
Yes |
This parameter holds the name of the connector class. Default Value: org.identityconnectors.workday.WorkdayConnector |
Bundle Name |
Yes |
This parameter holds the name of the connector bundle package. Default Value: org.identityconnectors.workday |
version |
Yes |
This parameter holds the version of Workday API you are using. Default Value: v34.1 |
pageCount |
Yes |
This parameter holds the number of records in each batch
that must be fetched from the target system during a reconciliation
run. While specifying a value for pageCount, ensure to specify
between Default Value: 100 |
workerWithAccount |
Yes |
Set the value to true if you want the parameter to reconcile only workers having a Workday account. Default Value: true |
timezone |
Yes |
This parameter holds the Workday timezone value. Default Value: PST |
4.3 Attribute Mapping for the Workday Authoritative Connector
The Schema page for an Authoritative application displays the default schema (provided by the connector) that maps Oracle Identity Governance attributes to target system columns. The connector uses these mappings during reconciliation operations.
Table 4-3 lists the user-specific attribute mappings between the reconciliation fields in Oracle Identity Governance and target system columns. The table also lists the data type for a given attribute and specifies whether it is a mandatory attribute for reconciliation.
You may use the default schema that has been set for you or update and change it before continuing to the next step. You can edit the attributes mappings by adding new attributes or deleting existing attributes on the Schema page as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.
Table 4-3 Workday Authoritative User Account Schema Attributes
Display Name | Target Attribute | Data Type | Mandatory Reconciliation Property? | Recon Field? | Default Value for Identity Display Name |
---|---|---|---|---|---|
Worker GUID |
__UID__ |
String |
No |
Yes |
Not Applicable |
User Login |
__NAME__ |
String |
No |
Yes |
Not Applicable |
Status |
__ENABLE__ |
String |
No |
Yes |
Not applicable |
First Name |
firstname |
String |
Yes |
Yes |
Not applicable |
Last Name |
lastName |
String |
Yes |
Yes |
Not applicable |
Display Name |
fullName |
String |
No |
Yes |
Not applicable |
|
emailAddressWork |
String |
No |
Yes |
Not applicable |
Telephone Number |
phoneNumberWork |
String |
No |
Yes |
Not applicable |
Home Phone |
phoneNumberHome |
String |
No |
Yes |
Not applicable |
Title |
positionTitle |
String |
No |
Yes |
Not applicable |
Postal Address |
streetAddress |
String |
No |
Yes |
Not applicable |
State |
state |
String |
No |
Yes |
Not applicable |
Country |
country |
String |
No |
Yes |
Not applicable |
Postal Code |
postalCode |
String |
No |
Yes |
Not applicable |
Start Date |
continousServiceDate |
Date |
No |
Yes |
Not applicable |
End Date |
terminationDate |
Date |
No |
Yes |
Not applicable |
Manager Login |
managerID |
String |
No |
Yes |
Not applicable |
Xellerate Type |
Long |
No |
Yes |
End-User |
|
Organization Name |
String |
No |
Yes |
Xellerate Users |
|
Role |
String |
No |
Yes |
Full-Time |
Figure 4-1 shows the default User account attribute mappings.
Figure 4-1 Workday Authoritative User Account Schema Attributes
![This is a screenshot of the Schema page for a trusted application that displays the default attribute mappings for an Workday Authoritative User account. This is a screenshot of the Schema page for a trusted application that displays the default attribute mappings for an Workday Authoritative User account.](img/trusted-schema-attribute-part1.png)
4.4 Correlation Rules for the Workday Authoritative Connector
When you create an Authoritative application, the connector uses correlation rules to determine the identity that must be reconciled into Oracle Identity Governance.
Predefined Identity Correlation Rules
By default, the Workday Authoritative connector provides a simple correlation rule when you create an Authoritative application. The connector uses this correlation rule to compare the entries in Oracle Identity Governance repository and the target system repository, determine the difference between the two repositories, and apply the latest changes to Oracle Identity Governance.
Table 4-4 lists the default simple correlation rule for Workday Authoritative application. If required, you can edit the default correlation rule or add new rules. You can create complex correlation rules also. For more information about adding or editing simple or complex correlation rules, see see Updating Identity Correlation Rule in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.
Table 4-4 Predefined Identity Correlation Rule for Workday Target Connector
Target Attribute | Element Operator | Identity Attribute | Case Sensitive? |
---|---|---|---|
__NAME__ |
Equals |
User Login |
No |
-
__NAME__ is a single-valued attribute on the target system that identifies the user account.
-
User Login is the field on the OIG User form.
Figure 4-2 shows the simple correlation rule for a Workday Target application.
Figure 4-2 Simple Correlation Rule for an Authoritative Application
![This is a screenshot of the Simple Correlation Rule when you create an Authoritative application. This is a screenshot of the Simple Correlation Rule when you create an Authoritative application.](img/new_corelationrule.jpg)
Predefined Situations and Responses
The Workday Authoritative connector provides a default set of situations and responses when you create an authoritative application. These situations and responses specify the action that Oracle Identity Governance must take based on the result of a reconciliation event.
Table 4-5 lists the default situations and responses for an authoritative application. If required, you can edit these default situations and responses or add new ones. For more information about adding or editing situations and responses, see Updating Identity Correlation Rule in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance
Table 4-5 Predefined Situations and Responses for an Authoritative Application
Situation | Response |
---|---|
No Matches Found |
Create User |
One Entity Match Found |
Establish Link |
4.5 Reconciliation Jobs for the Workday Authoritative Connector
These are the reconciliation jobs that are automatically created in Oracle Identity Governance after you create the application for your target system.
Workday Trusted User Reconciliation Job
You must specify values for the parameters of user reconciliation jobs.
The Workday Trusted User Reconciliation job is used to fetch all the workers from the target system.
You can either use these predefined jobs or edit them to meet your requirements. Alternatively, you can create custom reconciliation jobs. For information about editing these predefined jobs or creating new ones, see Updating Reconciliation Jobs in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.
Table 4-6 describes the parameters of the Workday Trusted User Reconciliation job.
Table 4-6 Parameters of the Workday Authoritative User Reconciliation Job
Parameter | Description |
---|---|
Application Name |
Name of the application you created for your target system. This value is the same as the value that you provided for the Application Name field while creating your target application. Do not modify this value. |
Filter Query |
Enter the search filter for fetching records from the target system during a reconciliation run. Sample value: For Performing Limited Reconciliation for more information about filtered reconciliation. |
Sync Token |
This attribute holds the date and time stamp at when the last full or incremental reconciliation run started. Default value:
Note:
|
Transaction Days |
Enter the number of days that corresponds to the official notice period of the organization or number of days a contractor hiring process is initiated before the original hire date, whichever is larger. Default value:
See Performing Reconciliation with Transaction Days for more information about reconciliation with Transaction Days. |
Object Type |
Type of the scheduled job you want to reconcile. Default value:
|
Scheduled Task Name |
Name of the scheduled job used for reconciliation. Default value:
Note: For the scheduled job included with this connector, you must not change the value of this attribute. However, if you create a new job or create a copy of the job, then enter the unique name for that scheduled job as the value of this attribute. |