rodrd.u00002vbzvL.20231024092422 (Partner) asked a question.
I'm having help connecting IGL to Google Workspace. Below I will describe the points where we encountered some blockers. The default connector, which would be Google Apps, is no longer viable because the required private key has been discontinued by Google. Therefore, we switched to a connection using Generic REST.
Collector: We were able to configure the OAuth 2.0 connection in the connector and collect groups and accounts, but IGL is not using the refresh token that is sent by the Google API. This means that after the current token expires, all calls will be terminated, preventing the process from continuing. Please see the screenshots below for reference:
Direct call to the Google Auth API, response returned:
Connector: In the connector, we are facing difficulties obtaining the access token. We tried using the same variable we used in the collector, but we were unsuccessful. Even after checking the AFX logs, we couldn't retrieve the necessary token to perform actions like account creation.
Additionally, the connector does not have an option to send the "scope" parameter, which is available in the collector. This makes it difficult to clearly define the actions that the token can execute.
Colector
Connector
Has anyone faced this challenge of integrating Google Workspace with IGL? if yes could you help me
with regards to the connector, you can add additional parameters like scope via the 'Add More Parameters' button.
Hello, I tried but according to the documentation, this add parameters only serves as parameters to be used within resources, it does not serve as additional information in the call header
I don't fully understand your comment.
Did you try to add scope parameter and it's still not working? What error are you seeing when trying to acquire a token in the connector?
What scope did you configure in the collector?