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).
Values are comma separated, and are in the following format: OBJ_CLASS. This entry specifies the HTTP operation type for each object class supported by this connector. "_ACCOUNT_.UPDATEOP=PUT","_ACCOUNT_.SEARCHOP=GET","_ACCOUNT_.DELETEOP=DELETE", "_ACCOUNT_._LICENSE_.UPDATEOP=POST", "_ACCOUNT_.licenseKeys.UPDATEOP=PUT","_ACCOUNT_.groupKey.UPDATEOP=PUT","_ACCOUNT_.CREATEOP=POST", This entry holds the name attribute for all the object classes that are handled by the connector.įor example, the value _ACCOUNT_.firstName in decode 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. "_ACCOUNT_.firstName","_GROUP_.name","_LICENSE_.description" This entry holds the JSON tag value that is used during reconciliation for parsing multiple entries in a single payload. "_ACCOUNT_=results","_GROUP_=results","_LICENSE_=results" This entry holds the content type expected by the target system in the request header. This entry holds the accept type expected from the target system in the request header. This entry lists the request payload formats for all the connector operations that are not in standard JSON format. This entry holds the name of the connector class. This entry holds the version of the connector bundle.
This entry holds the name of the connector bundle.
Gotomeeting admin code#
Table 3-2 Entries in the Lookup Definition Code Key The bundle then passes it to the adapters. 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. Therefore, you do not need to configure or modify ICF.ĭuring 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. ICF is distributed together with Oracle Identity Manager. 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 component provides basic reconciliation and provisioning operations that are common to all Oracle Identity Manager connectors. Through reconciliation, account data that is created and updated directly on the Admin Center is fetched into Oracle Identity Manager and stored against the corresponding Oracle Identity Manager Users. Through the provisioning operations that are performed on Oracle Identity Manager, accounts are created and updated on the Admin Center for Oracle Identity Manager Users. Figure 3-1 Architecture of the GoToMeeting Connectorĭescription of "Figure 3-1 Architecture of the GoToMeeting Connector"Īs shown in Figure 3-1, the Admin Center is configured as a target resource of Oracle Identity Manager.
0 kommentar(er)
