About the GoToMeeting Connector

3.1 About the GoToMeeting Connector

The GoToMeeting connector can be configured to run in the Target (account management) mode. In this mode, the Admin Center is used as a target (managed) resource of the identity data for Oracle Identity Governance.

The following topics provide a high-level overview of the connector:

3.1.1 Certified Components for the GoToMeeting Connector

These are the software components and their versions required for installing and using the GoToMeeting connector.

Note:

If you are using Oracle Identity Manager release 11.1.x, then you can install and use the connector only in the CI-based mode. If you want to use the AOB application, then you must upgrade to Oracle Identity Governance release 12.2.1.3.0.

Table 3-1 Certified Components for the GoToMeeting Connector

Component	Requirement for AOB Application	Requirement for CI-Based Connector
Oracle Identity Governance or Oracle Identity Manager	You can use any one of the following releases: Oracle Identity Governance release 12c PS4 (12.2.1.4.0) Oracle Identity Governance 12c (12.2.1.3.0) Note: If you are using Oracle Identity Governance 12c (12.2.1.3.0), then ensure to download and apply patches 26616250 and 25323654 from My Oracle Support.	You can use one of the following releases of Oracle Identity Governance or Oracle Identity Manager: Oracle Identity Governance release 12c PS4 (12.2.1.4.0) Oracle Identity Governance 12c (12.2.1.3.0) Oracle Identity Manager 11g Release 2 PS3 BP06 (11.1.2.3.6)
Target system	GoToMeeting Admin Center	GoToMeeting Admin Center
Connector Server	11.1.2.1.0 or later	11.1.2.1.0 or later
Connector Server JDK	JDK 1.8 or later	JDK 1.8 or later

3.1.2 Usage Recommendation for the GoToMeeting Connector

These are the recommendations for the GoToMeeting connector versions that you can deploy and use depending on the Oracle Identity Governance or Oracle Identity Manager version that you are using.

If you are using Oracle Identity Governance release 12c (12.2.1.3.0) or later, then use the latest 12.2.1.x version of this connector. Deploy the connector using the Applications option on the Manage tab of Identity Self Service.
If you are using the Oracle Identity Manager release listed in the “Requirement for CI-Based Connector” column in Certified Components for the GoToMeeting Connector, then use the 11.1.x version of the connector. If you want to use the 12.2.1.x version of this connector, then you can install and use it only in the CI-based mode. If you want to use the AOB application, then you must upgrade to Oracle Identity Governance release 12c (12.2.1.3.0) or later.

Note:

If you are using the latest 12.2.1.x version of the GoToMeeting connector in the CI-based mode, then see Oracle Identity Manager Connector Guide for GoToMeeting, Release 11.1.1 for complete details on connector deployment, usage, and customization.

3.1.3 Certified Languages for the GoToMeeting Connector

These are the languages that the connector supports.

Arabic
Chinese (Simplified)
Chinese (Traditional)
Czech
Danish
Dutch
English (US)
Finnish
French
French (Canadian)
German
Greek
Hebrew
Hungarian
Italian
Japanese
Korean
Norwegian
Polish
Portuguese
Portuguese (Brazilian)
Romanian
Russian
Slovak
Spanish
Swedish
Thai
Turkish

3.1.4 Operations Supported by the GoToMeeting Connector

These are the list of operations that the connector supports.

Table 3-2 Supported Connector Operations for the GoToMeeting Connector

Operation	Supported?
User Management
Create user	Yes
Update user	Yes
Delete user	Yes
Entitlement Grant Management
Add child table values	Yes
Update child table values	Yes
Remove child table values	Yes

3.1.5 Architecture of the GoToMeeting Connector

You can configure the GoToMeeting connector to run in the Target (or account management) mode, and is implemented using the Identity Connector Framework (ICF) component.

The ICF is a component that provides basic reconciliation and provisioning operations that are common to all Oracle Identity Governance connectors. In addition, ICF provides common features that developers would otherwise need to implement on their own, such as connection pooling, buffering, time outs, and filtering. The ICF is shipped along with Oracle Identity Governance. Therefore, you need not configure or modify the ICF.

The connector enables the following operations:

Provisioning

Provisioning involves creating and updating users on the Admin Center through Oracle Identity Governance. When you allocate (or provision) a GoToMeeting resource to an Oracle Identity Governance User, the operation results in the creation of an account in the Admin Center for that user. In the Oracle Identity Governance context, the term provisioning is also used to mean updates made to the account through Oracle Identity Governance.
Target resource reconciliation

To perform target resource reconciliation, the GoToMeeting Reconciliation job is used. The connector then fetches the user attribute values from the Admin Center.

The connector supports OAuth 2.0 security protocol for authenticating to the target system, and uses access token and refresh token values as inputs from the user.

Figure 3-1 depicts the architecture of the GoToMeeting connector.

Figure 3-1 Architecture of the GoToMeeting Connector

Description of "Figure 3-1 Architecture of the GoToMeeting Connector"

As shown in Figure 3-1, the Admin Center is configured as a target resource of Oracle Identity Governance. Through the provisioning operations that are performed on Oracle Identity Governance, accounts are created and updated on the Admin Center for Oracle Identity Governance Users.

Through reconciliation, account data that is created and updated directly on the Admin Center is fetched into Oracle Identity Governance and stored against the corresponding Oracle Identity Governance Users.

The ICF component provides basic reconciliation and provisioning operations that are common to all Oracle Identity Governance connectors. In addition, ICF provides common features that developers would otherwise need to implement on their own, such as connection pooling, buffering, time outs, and filtering. ICF is distributed together with Oracle Identity Governance. Therefore, you do not need to configure or modify ICF.

During provisioning, the adapters invoke ICF operation, ICF invokes the Create operation on GoToMeeting Connector Bundle, and then the bundle calls the OAuth API for connecting to the Admin Center and performing user authentication. The Admin Center accepts provisioning data from the bundle using GoToMeeting Administration APIs , carries out the operation, and returns the response back to the bundle. The bundle then passes it to the adapters.

3.1.6 Supported Features Matrix for the GoToMeeting Connector

Provides the list of features supported by the AOB application and CI-based connector.

Table 3-3 Supported Features Matrix for the GoToMeeting Connector

Feature	AOB Application	CI-Based Connector
Clone applications or create new application instances	Yes	Yes
Perform user provisioning	Yes	Yes
Perform full reconciliation	Yes	Yes
Perform limited reconciliation	Yes	Yes
Configure validation and transformation of account data	Yes	Yes
Use connector server	Yes	Yes
Provide secure communication to the target system through SSL	Yes	Yes

3.1.7 Features of the GoToMeeting Connector

The features of the connector include support for provisioning user accounts, target resource reconciliation, reconciliation of all existing account data, limited reconciliation, transformation and validation of account data during reconciliation and provisioning, support for the connector server, multiple installations of the target system, secure communication to the target system through SSL, and so on.

The following are the features of this connector:

3.1.7.1 Support for User Account Provisioning

You can use the connector for provisioning user accounts.

You perform provisioning operations in Oracle Identity Governance by using the Create User page. See Creating a User in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance for details about the fields on the Create User page.

3.1.7.2 Support for Full Reconciliation

After you create the application, you can perform full reconciliation to bring all existing user data from the target system to Oracle Identity Governance.

You can perform a full reconciliation run at any time. See Performing Full Reconciliation.

3.1.7.3 Support for Limited Reconciliation

You can set a reconciliation filter as the value of the Filter attribute of the scheduled tasks. This filter specifies the subset of newly added and modified target system records that must be reconciled.

To limit or filter the records that are fetched into Oracle Identity Governance during a reconciliation run, see Performing Limited Reconciliation.

3.1.7.4 Support for the Connector Server

Connector Server is one of the features provided by ICF. By using one or more connector servers, the connector architecture permits your application to communicate with externally deployed bundles.

A Java connector server is useful when you do not wish to execute a Java connector bundle in the same VM as your application. It can be beneficial to run a Java connector on a different host for performance improvements.

For information about installing, configuring, and running the Connector Server, and then installing the connector in a Connector Server, see Using an Identity Connector Server in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.

3.1.7.5 Support for Cloning Applications and Creating Instance Applications

You can configure this connector for multiple installations of the target system by cloning applications or by creating instance applications.

When you clone an application, all the configurations of the base application are copied into the cloned application. When you create an instance application, it shares all configurations as the base application.

For more information about these configurations, see Cloning Applications and Creating Instance Applications in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

3.1.7.6 Secure Communication to the Target System

To provide secure communication to the target system, SSL is required. You can configure SSL between Oracle Identity Governance and the Connector Server and between the Connector Server and the target system.

If you do not configure SSL, passwords can be transmitted over the network in clear text. For example, this problem can occur when you are creating a user or modifying a user's password.

See Configuring SSL for the Connector.

3.1.7.7 Transformation and Validation of Account Data

You can configure transformation and validation of account data that is brought into or sent from Oracle Identity Governance during reconciliation and provisioning operations by writing Groovy scripts while creating your application.

For more information, see Validation and Transformation of Provisioning and Reconciliation Attributes in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.