2 Creating an Application by Using the WebEx Connector

Learn about onboarding applications using the connector and the prerequisites for doing so.

2.1 Process Flow for Creating an Application By Using the Connector

From Oracle Identity Governance release 12.2.1.3.0 onward, connector deployment is handled using the application onboarding capability of Identity Self Service.

Figure 2-1 is a flowchart depicting high-level steps for creating an application in Oracle Identity Governance by using the connector installation package.

Figure 2-1 Overall Flow of the Process for Creating an Application By Using the Connector

Description of Figure 2-1 follows
Description of "Figure 2-1 Overall Flow of the Process for Creating an Application By Using the Connector"

2.2 Prerequisites for Creating an Application By Using the Connector

Learn about the tasks that you must complete before you create the application.

2.2.1 Configuring the Target System

Configuring the Target System involves creating a WebEx service account on the target system to manage users on WebEx through Oracle Identity Governance and registering a client application with the target system so that the connector can access WebEx XML APIs.

Perform the following procedure to create a service user account on the target system.

Note:

The detailed instructions for performing these preinstallation tasks are available in the WebEx product documentation at http://www.cisco.com/.

To configure the target system:

  1. Login to the WebEx application using the Admin account.

  2. Create a WebEx service user account on the target system to manage users on WebEx through Oracle Identity Manager.

  3. Register the client application of the connector to provide a secure sign-in and authorization for your services.

  4. From the Site Administration link, create a user with Account Type as Site Administrator and provide values for all the mandatory fields required for user creation.

  5. Login with the new user credentials and from the Site Administration link, copy the SiteID and PartnerID values which needs to be updated in the Basic Configuration while configuring WebEx connector.

2.2.2 Downloading the Connector Installation Package

You can obtain the installation package for your connector on the Oracle Technology Network (OTN) website.

To download the connector installation package:
  1. Navigate to the OTN website at http://www.oracle.com/technetwork/middleware/id-mgmt/downloads/connectors-101674.html.
  2. Click OTN License Agreement and read the license agreement.
  3. Select the Accept License Agreement option.
    You must accept the license agreement before you can download the installation package.
  4. Download and save the installation package to any directory on the computer hosting Oracle Identity Governance.
  5. Extract the contents of the installation package to any directory on the computer hosting Oracle Identity Governance. This creates a directory named CONNECTOR_NAME-RELEASE_NUMBER.
  6. Copy the CONNECTOR_NAME-RELEASE_NUMBER directory to the OIG_HOME/server/ConnectorDefaultDirectory directory.

2.3 Creating an Application By Using the Connector

You can onboard an application into Oracle Identity Governance from the connector package by creating a Target application. To do so, you must log in to Identity Self Service and then choose the Applications box on the Manage tab.

The following is the high-level procedure to create an application by using the connector:

Note:

For detailed information on each of the steps in this procedure, see Creating Applications of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

  1. Create an application in Identity Self Service. The high-level steps are as follows:
    1. Log in to Identity Self Service either by using the System Administration account or an account with the ApplicationInstanceAdministrator admin role.
    2. Ensure that the Connector Package option is selected when creating an application.
    3. Update the basic configuration parameters to include connectivity-related information.
    4. If required, update the advanced setting parameters to update configuration entries related to connector operations.
    5. Review the default user account attribute mappings. If required, add new attributes or you can edit or delete existing attributes.
    6. Review the provisioning, reconciliation, organization, and catalog settings for your application and customize them if required. For example, you can customize the default correlation rules for your application if required.
    7. Review the details of the application and click Finish to submit the application details. The application is created in Oracle Identity Governance.
    8. When you are prompted whether you want to create a default request form, click Yes or No.

      If you click Yes, then the default form is automatically created and is attached with the newly created application. The default form is created with the same name as the application. The default form cannot be modified later. Therefore, if you want to customize it, click No to manually create a new form and attach it with your application.

  2. Add values for the Lookup.Webex.MeetingTypes lookup, as follows:
    1. Login to Identity Sytem Administration either by using the System Administration account or an account with the ApplicationInstanceAdministrator admin role.
    2. Click Lookups, and search for Lookup.Webex.MeetingTypes. Click Edit Lookup Type, and add values for this static lookup. For example:
      Meaning Code
      Webex~AUO 49~16
      Webex~PRO 49~113
      Webex~ONS 49~129
      Webex~TRS 49~128
      Webex~SC3 49~13

      Here, 49 is the IT resource key.

  3. Verify provisioning and reconciliation operations on the newly created application.

See Also:

  • Configuring the WebEx Connector for details on basic configuration and advanced settings parameters, default user account attribute mappings, default correlation rules, and reconciliation jobs that are predefined for this connector

  • Configuring Oracle Identity Governance for details on creating a new form and associating it with your application, if you chose not to create the default form