Supported Features

The Oracle E-Business connector supports the following features:

  • Load and *Provision

    • Oracle E-Business accounts

    • Responsibilities

    • Roles

  • *Access Certifications (certification of entitlements connected to accounts)

  • *Password management

For more information on features, refer to Identity Security Cloud Source Features.

Note
Before you can use any item above marked with an asterisk (*), SailPoint must activate the feature for your site.

The Oracle E-Business source supports the following multiple group and entitlement objects:

Source Objects

Supported Operation

RESPONSIBILITY as RESPONSIBILITY object

Read

ROLE as ROLE object

Read

ROLE and RESPONSIBILITY as entitlement objects

Add / Remove entitlement

The following ROLE schema attributes are supported:

  • NAME

  • DISPLAY_NAME

  • DESCRIPTION

  • START_DATE

  • EXPIRATION_DATE

  • APPLICATION_NAME

  • STATUS

  • SUBORDINATE_ROLES

The following RESPONSIBILITY schema attributes are supported:

  • RESPONSIBILITY_NAME

  • APPLICATION_NAME

  • RESPONSIBILITY_ID

  • RESPONSIBILITY_KEY

  • START_DATE

  • END_DATE

  • DESCRIPTION

  • STATUS

  • VERSION

  • WEB_HOST_NAME

  • WEB_AGENT_NAME

  • DATA_GROUP_APPL_NAME

  • REQUEST_GROUP_APPL_NAME

  • DATA_GROUP_ID

  • DATA_GROUP_NAME

  • MENU_NAME

  • REQUEST_GROUP_NAME

Using Multiple Group Objects for Pre-existing Sources

  1. Use createSchema API to create new group schema for your source.

  2. Update Account Schema with the following steps:

    1. Get account schema using getSchema API.

    2. Copy the schema to a file and search for the attribute corresponding to the group schema that is added in the previous step. Add/update the below two properties for the attribute found in the previous step "isGroup": true, "schema": {"type": "CONNECTOR_SCHEMA","id": "<Schema_ID_From_Step1>","name": "<Name_Of_Schema_Created_In_Step1>"}

    3. Add the modified schema to the payload to update the account schema in the source using replaceSchema API

ROLE Hierarchy

The ROLE schema has the SUBORDINATE_ROLES attribute that holds the hierarchy of ROLE. The hierarchy attribute can be defined and childHierarchy can be used to set the correct parent-child relationship. To display the child hierarchy of the Role, you must remove the convertListToCSV configuration attribute (related to the list) to the CSV from the source template.

API to add new ROLE schema

Details

Method: POST

URL: beta/sources/<source-id>/schemas

JSON Payload example:

Copy 
{
"nativeObjectType": "ROLE",
"identityAttribute": "NAME",
"displayAttribute": "DISPLAY_NAME",
"hierarchyAttribute": "SUBORDINATE_ROLES",
"includePermissions": false,
"features": [],
"configuration": {
"childHierarchy": "true"
},
"attributes": [
{
"name": "NAME",
"type": "STRING",
"schema": null,
"description": "An internal name for the role",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "DISPLAY_NAME",
"type": "STRING",
"schema": null,
"description": "The display name of the role",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "DESCRIPTION",
"type": "STRING",
"schema": null,
"description": "DESCRIPTION",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "START_DATE",
"type": "STRING",
"schema": null,
"description": "The date at which the role becomes valid",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "EXPIRATION_DATE",
"type": "STRING",
"schema": null,
"description": "The date at which the role is no longer
valid in the directory service",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "APPLICATION_NAME",
"type": "STRING",
"schema": null,
"description": "Application that owns the information for the role",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "STATUS",
"type": "STRING",
"schema": null,
"description": "The availability of the
Role to participate in a workflow process",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "SUBORDINATE_ROLES",
"type": "STRING",
"schema": null,
"description": "Subordinate roles for a role",
"isMulti": true,
"isEntitlement": true,
"isGroup": false
}
],
"id": "2c91808f79180d49017918643cb60153",
"name": "ROLE",
"created": "2021-01-25T12:07:25.596Z",
"modified": null
}

API to add new MENU schema

Details

Method: POST

URL: beta/sources/<source-id>/schemas

JSON Payload example:

Copy 
{
"nativeObjectType": "MENU",
"identityAttribute": "MENU_ID",
"displayAttribute": "MENU_NAME",
"hierarchyAttribute": "SUB_MENU",
"includePermissions": false,
"features": [],
"configuration": {
"childHierarchy": "true"
},
"attributes": [
{
"name": "MENU_ID",
"type": "STRING",
"schema": null,
"description": "An internal ID for the menu",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "MENU_NAME",
"type": "STRING",
"schema": null,
"description": "The name of the menu",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "TYPE",
"type": "STRING",
"schema": null,
"description": "The type of menu",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
{
"name": "SUB_MENU",
"type": "STRING",
"schema": null,
"description": "The list of sub-menus",
"isMulti": true,
"isEntitlement": true,
"isGroup": false
},
{
"name": "FUNCTION_NAME",
"type": "STRING",
"schema": null,
"description": "The functions assigned to a menu",
"isMulti": false,
"isEntitlement": false,
"isGroup": false
},
"id": "2c91808f79180d49017918643cb60153",
"name": "MENU",
"created": "2021-01-25T12:07:25.596Z",
"modified": null
}