3.3.1 Attribute Mappings for the Target Application

The Schema page for a target application displays the default schema (provided by the connector) that maps Oracle Identity Governance attributes to target system attributes. The connector uses these mappings during reconciliation and provisioning operations.

The following table lists the user-specific attribute mappings between the process form fields in Oracle Identity Governance and Jira target application attributes. The table also lists whether a specific attribute is used during provisioning or reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-3 Default Attributes for Jira Target Application

Display Name Target Attribute Data Type Mandatory Provisioning Property? Provision Field? Recon Field? Key Field? Case Insensitive?
accountId __UID__ String No No Yes Yes Yes
DisplayName __NAME__ String No No Yes No Not applicable
accountType accountType String No No Yes No Not applicable
active active String No No Yes No Not applicable
Status __ENABLE__ String No No Yes No Not applicable
Email emailAddress String No Yes No No Not applicable
Timezone timezone String No No Yes No Not applicable
Locale locale String No No Yes No Not applicable
IT Resource Name   Long No No Yes No Not applicable

The following figure shows the default User account attribute mappings.

Figure 3-1 Default Attribute Mappings for Jira User Account

Default Attribute Mappings for Jira User Account

Jira Group Entitlement

The following table lists the Groups forms attribute mappings between the process form fields in Oracle Identity Governance and Jira target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-4 Default Attribute Mappings for Groups

Display Name Target Attribute Data Type Mandatory Provisioning Property? Recon Field? Key Field? Case Insensitive?
Group Name groupId String No Yes Yes No
Following figure shows the default Groups Entitlement mapping.

Figure 3-2 Default Attribute Mappings for Jira Groups

Default Attribute Mappings for Jira Groups