Configuring the GoToMeeting Connector

3.3.1 Basic Configuration Parameters

These are the connection-related parameters that Oracle Identity Governance requires to connect to GoToMeeting.

Table 3-4 Basic Configuration Parameters for GoToMeeting

Parameter	Mandatory?	Description
authenticationType	Yes	Type of authentication that is used by your target system. This connector supports authenticating to the target system by using OAuth 2.0 custom authentication type. Default value: `Other` Do not modify the value of the parameter.
clientId	No	Enter the consumer key value that is generated after creating the developer application. Sample value: `ABCDEbkTacBC7emdnbABCDEFa96DsEYN` See Configuring the Target System for details on obtaining the consumer key value.
clientSecret	No	Enter the consumer secret value that is generated after creating the developer application. Sample value: `AB9CDoOOabCo2l03` See Configuring the Target System for details on obtaining the consumer secret value.
customAuthHeaders	No	Enter the access token and refresh token values in the following format: `“access_token=ACCESSTOKEN”`,`“refresh_token=REFRESHTOKEN”` In this format, replace `ACCESSTOKEN` with the access token value and `REFRESHTOKEN` with the refresh token value. These values are generated after setting up the Developer Sandbox. Sample value: `access_token=ABabEXAMPLe0Q0ZjABCabc0AbAbC","refresh_token=hABCfd9oABc6abcDeFGabcdXhwRMIHav"` See Configuring the Target System for details on obtaining the access token and refresh token values.
host	Yes	Enter the host name of your target system. Sample value: `api.getgo.com`
uriPlaceHolder	No	Enter the account key value that is displayed while generating the access token and refresh token values for your Developer Sandbox account. Sample value: `“account_key;5253092000266355206”` See Configuring the Target System for details on obtaining the account key value.
Connector Server Name	No	If you have deployed the GoToMeeting connector in the Connector Server, then enter the name of the IT resource of type "Connector Server". By default, this field is blank. If you have deployed the connector in a Java Connector Server, then enter the name of the IT resource for the Connector Server.
port	No	Enter the port number at which the target system is listening. Sample value: `443`
proxyHost	No	Enter the name of the proxy host that is used to connect to an external target system. Sample value: `proxy.gotomeeting.com`
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: `80`
proxyUser	No	Enter the proxy user name of the target system user account that Oracle Identity Governance uses to connect to the target system. Sample value: `johnsmith`
sslEnabled	No	If the target system requires SSL connectivity, then set the value of this parameter to `true`. Otherwise set the value to `false`. Default value: `true`

3.3.2 Advanced Settings Parameters

These are the configuration-related entries that the connector uses during reconciliation and provisioning operations.

Table 3-5 Advanced Settings Parameters for GoToMeeting

Parameter	Mandatory?	Description
nameAttributes	Yes	This entry holds the name attribute for all the object classes that are handled by the connector. Default value: `"__ACCOUNT__.firstName","__GROUP__.name","__LICENSE__.description"` In this default value, the `__ACCOUNT__.firstName` value implies that the `name` attribute of the connector for `__ACCOUNT__` object class is mapped to `firstName`, which is the corresponding name attribute for User account in the target system.
relURIs	Yes	This entry holds the relative URL for all operations supported by the connector for each object class. Default value: `"__ACCOUNT__.licenseKeys.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/licenses/$(licenseKeys)$/users/$(__UID__)$",` `"__ACCOUNT__.CREATEOP=/admin/rest/v1/accounts/$(account_key)$/users",` `"__ACCOUNT__.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/users/$(__UID__)$",` `"__ACCOUNT__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/users?$(Filter Suffix)$&pageSize=$(PAGE_SIZE)$&offset=$(PAGE_OFFSET)$",` `"__ACCOUNT__.DELETEOP=/admin/rest/v1/accounts/$(account_key)$/users/$(__UID__)$",` `"__ACCOUNT__.__ROLE__.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/users/$(__UID__)$",` `"__LICENSE__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/licenses?pageSize=$(PAGE_SIZE)$&offset=$(PAGE_OFFSET)$",` `"__ACCOUNT__.__LICENSE__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/licenses?pageSize=$(PAGE_SIZE)$&offset=$(PAGE_OFFSET)$",` `"__GROUP__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/groups? pageSize=$(PAGE_SIZE)$&offset=$(PAGE_OFFSET)$",` `"__ACCOUNT__.__LICENSE__.ADDATTRIBUTE=/admin/rest/v1/accounts/$(account_key)$/licenses/$(__LICENSE__.key)$/users/$(__UID__)$",` `"__ACCOUNT__.__LICENSE__.REMOVEATTRIBUTE=/admin/rest/v1/accounts/$(account_key)$/licenses/$(__LICENSE__.key)$/users/$(__UID__)$",` `"__ACCOUNT__.groupKey.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/groups/$(groupKey)$/users/$(__UID__)$"` In this default value, the `__ACCOUNT__.CREATEOP=/admin/rest/v1/accounts/$(account_key)$/users` value implies that `/admin/rest/v1/accounts/$(account_key)$/users` is the relative URL for all create provisioning operations that are performed on the `__ACCOUNT__` object class.
uidAttributes	Yes	This entry holds the UID attribute for all the object classes that are handled by the connector. Default value: `"__ACCOUNT__.key","__GROUP__.key","__LICENSE__.key"` In this default value, the `__ACCOUNT__.key` value implies that the `__UID__` attribute (that is, GUID) of the connector for `__ACCOUNT__` object class is mapped to `key`, which is the corresponding UID attribute for User account in the target system.
Bundle Version	No	This entry holds the version of the connector bundle class. Do not modify this entry. Default value: `12.3.0`
Bundle Name	No	This entry holds the name of the connector bundle package. Default value: `org.identityconnectors.genericrest` Do not modify this entry.
simpleMultivaluedAttribute	No	This entry holds the name of the attributes that can hold multiple values. Default value: `"__ACCOUNT__=primaryLicense"` In this default value, the `primaryLicense` attribute holds the value as `License` because multiple licenses can be assigned to a user account.
Connector Name	No	This entry holds the name of the connector class. Default value: `org.identityconnectors.genericrest.GenericRESTConnector`
customPayload	No	This entry lists the request payload formats for all the connector operations that are not in standard JSON format. Default value: `"__ACCOUNT__.CREATEOP={\"users\":[{\"email\":\"$(email)$\",\"firstName\":\"$(__NAME__)$\",\"lastName\":\"$(lastName)$\",` `\"locale\":\"$(locale)$\"}],\"groupKey\":\"$(groupKey)$\",\"licenseKeys\":[$(licenseKeys)$]}"`
jsonResourcesTag	No	This entry holds the JSON tag value that is used during reconciliation for parsing multiple entries in a single payload. Default value: `"__ACCOUNT__=results","__GROUP__=results","__LICENSE__=results"`
httpHeaderContentType	No	This entry holds the content type expected by the target system in the request header. Default value: `application/json`
httpHeaderAccept	No	This entry holds the accept type expected from the target system in the request header. Default value: `application/json`
opTypes	No	This entry specifies the HTTP operation type for each object class supported by this connector. Default value: `"__ACCOUNT__.licenseKeys.UPDATEOP=PUT","__ACCOUNT__.groupKey.UPDATEOP=PUT","__ACCOUNT__.CREATEOP=POST",` `"__ACCOUNT__.UPDATEOP=PUT","__ACCOUNT__.SEARCHOP=GET","__ACCOUNT__.DELETEOP=DELETE", "__ACCOUNT__.__LICENSE__.UPDATEOP=POST",` `"__ACCOUNT__.__LICENSE__.DELETEOP=DELETE"` Values are comma separated, and are in the following format: OBJ_CLASS.OP=HTTP_OP In this format, OBJ_CLASS is the connector object class, OP is the connector operation (for example, CreateOp, UpdateOp, SearchOp), and HTTP_OP is the HTTP operation (GET, PUT, or POST).
specialAttributeHandlling	No	This entry lists the special attribute, which is an attribute in an object class that can be managed only through a separate REST API endpoint rather than the same endpoint of the base object class. Default value: `"__ACCOUNT__.__LICENSE__.ADDATTRIBUTE=SINGLE","__ACCOUNT__.__LICENSE__.REMOVEATTRIBUTE=SINGLE",` `"__ACCOUNT__.__LICENSE__.CREATEOP=SINGLE","__ACCOUNT__.__LICENSE__.UPDATEOP=SINGLE",` `"__ACCOUNT__.licenseKeys.UPDATEOP=SINGLE", "__ACCOUNT__.groupKey.UPDATEOP=SINGLE"` Values are sent to the target system in separate calls, one at a time. In addition, values are comma separated, and are in the following format: OBJ_CLASS.ATTR_NAME.PROV_OP=SINGLE For example, the `__ACCOUNT__.groupKey.UPDATEOP=SINGLE` value in decode implies that during an update provisioning operation, values for the `groupKey` attribute of the `__ACCOUNT__` object class is sent to the target system in separate calls, one at a time.
specialAttributeTargetFormat	No	This entry lists the format in which a special attribute is present in the target system response. Default value: `"__ACCOUNT__.__GROUP__=managedGroupKeys","__ACCOUNT__.__LICENSE__=licenseKeys"` For example, the `__ACCOUNT__.__LICENSE__` attribute is present as `licenseKeys` in the target system response. Values are comma separated, and are presented in the following format: OBJ_CLASS.ATTR_NAME= TARGET_FORMAT

3.3.3 Attribute Mappings

The Schema page for a Target 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 and provisioning operations.

GoToMeeting User Account Attributes

This table lists the mapping of attribute between the process form fields and GoToMeeting columns. 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 of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-6 Default Attribute Mappings for GoToMeeting User Account

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Provision Field?	Recon Field	Key Field?	Case Insensitive?
User key	__UID__	String	No	Yes	Yes	Yes	NA
First Name	__NAME__	String	Yes	Yes	Yes	No	NA
Last Name	lastName	String	Yes	Yes	Yes	No	NA
Group	groupKey	String	No	Yes	Yes	No	NA
Locale	locale	String	Yes	Yes	Yes	No	NA
Email	email	String	Yes	Yes	Yes	Yes	Yes
PrimaryLicense	licenseKeys	String	Yes	Yes	Yes	No	NA
IT Resource	NA	Long	Yes	No	Yes	Yes	NA

Figure 3-3 shows the default GoToMeeting User account attribute mapping.

Figure 3-3 Default Attribute Mappings for GoToMeeting User Account

Description of "Figure 3-3 Default Attribute Mappings for GoToMeeting User Account"

Licenses Entitlement Attributes

This is the default mapping of attributes between process form fields and licenses-related columns in the target system. 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 of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-7 Default Attribute Mappings for Licenses Entitlement

Display Name	Application Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
License Name	__LICENSE__~__LICENSE__~key	String	No	Yes	Yes	No

Figure 3-4 shows the default Licenses entitlement mapping.

Figure 3-4 Default Attribute Mappings for Licenses Entitlement

Description of "Figure 3-4 Default Attribute Mappings for Licenses Entitlement"

3.3.4 Rules, Situations, and Responses

Learn about the predefined rules, situations, and responses for a GoToMeeting Target application. The connector use these rules and responses for performing reconciliation.

Predefined Identity Correlation Rules

By default, the GoToMeeting connector provides a simple correlation rule when you create a Target 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 3-8 lists the default simple correlation rule for the GoToMeeting connector. 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 Updating Identity Correlation Rule in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-8 Predefined Identity Correlation Rule for GoToMeeting

Target Attribute	Element Operator	Identity Attribute	Case Sensitive?
email	Equals	Email	No

In this identity rule:

email is a single-valued attribute on the target system that identifies the user account.
Email is the field on the OIG User form.

Figure 3-5 shows the simple correlation rule for the GoToMeeting connector.

Figure 3-5 Simple Correlation Rule for GoToMeeting

Description of "Figure 3-5 Simple Correlation Rule for GoToMeeting"

Predefined Situations and Responses

The GoToMeeting connector provides a default set of situations and responses when you create a Target application. These situations and responses specify the action that Oracle Identity Governance must take based on the result of a reconciliation event.

Table 3-9 lists the default situations and responses for the GoToMeeting connector. 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 Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-9 Predefined Situations and Responses for GoToMeeting

Situation	Response
No Matches Found	None
One Entity Match Found	Establish Link
One Process Match Found	Establish Link

Figure 3-6 shows the situations and responses that the connector provides by default.

Figure 3-6 Predefined Situations and Responses for GoToMeeting

Description of "Figure 3-6 Predefined Situations and Responses for GoToMeeting "

3.3.5 Reconciliation Jobs

Learn about reconciliation jobs that are automatically created in Oracle Identity Governance after you create a target application for your target system.

GoToMeeting Full User Reconciliation Job

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.

The GoToMeeting Full User Reconciliation job is used to fetch all user records from the target system.

Table 3-10 Parameters of the GoToMeeting Full User Reconciliation Job

Parameter	Value
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 Suffix	Enter the search filter for fetching user records from the target system during a reconciliation run. Sample value: `filter=firstName %20%3D%20%22.UserA.%22` See Performing Limited Reconciliation.
Object Type	Type of object you want to reconcile. Default value: `User`
Scheduled Task Name	This attribute holds the name of the scheduled task. Default value: `GoToMeeting Full User Reconciliation` Do not modify this value.

Reconciliation Jobs for Entitlements

The following jobs are available for reconciling entitlements:

GoToMeeting Licenses Lookup Reconciliation: Use this job to reconcile all licenses-related data in the target system into lookup fields in Oracle Identity Governance.
GoToMeeting Group Lookup Reconciliation: Use this job to reconcile all group data in the target system into lookup fields in Oracle Identity Governance.

The parameters for all the reconciliation jobs are the same.

Table 3-11 Parameters of the Reconciliation Jobs for Entitlements

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.
Lookup Name	This parameter holds the name of the lookup definition that maps each lookup definition with the data source from which values must be fetched. Depending on the reconciliation job that you are using, the default values are as follows: GoToMeeting Licenses Lookup Reconciliation: `Lookup.GTM.License` GoToMeeting Group Lookup Reconciliation: `Lookup.GTM.Group`
Object Type	Enter the type of object whose values must be synchronized. Depending on the scheduled job that you are using, the default values are as follows: GoToMeeting Licenses Lookup Reconciliation: `__LICENSE__` GoToMeeting Group Lookup Reconciliation: `__GROUP__` Do not modify this value.
Code Key Attribute	Enter the name of the connector or target system attribute that is used to populate the Code Key column of the lookup definition (specified as the value of the Lookup Name attribute). Default value: `__UID__` Do not modify this value.
Decode Attribute	Enter the name of the connector or target system attribute that is used to populate the Decode column of the lookup definition (specified as the value of the Lookup Name attribute). Default value: `__NAME__`