Skip to main content
  • EN
  • Home
  • Forums
  • FME Form
  • General
  • I have a workbench which has the GoogleDrive Connector in it which downloaded files to a local folder for me however it has stopped working and I get an Authorisation Error 400. When I go to authenticate my web service I get the attached message

and error message below. Not sure where to from here. It was working but I am a total novice at web connection stuff.

2023-06-01 15:11:03| 0.9| 0.0|WARN |Request to update access token failed. HTTP Error: HTTP/1.1 400 Bad Request

2023-06-01 15:11:03| 0.9| 0.0|ERROR |Python Exception <FMEWSException>: Type: 3, Number: 1, Message: Failed to get authorization header.

2023-06-01 15:11:03| 0.9| 0.0|ERROR |Traceback (most recent call last):

File "fmegeneral\\plugins.py", line 500, in input

File "webserviceconnector\\fmewebfs.py", line 1096, in receive_feature

File "googledrive\\gdrivefs.py", line 569, in handle_operation

File "webserviceconnector\\fmewebfs.py", line 699, in handle_operation

File "webserviceconnector\\fmewebfs.py", line 856, in handle_download

File "googledrive\\gdrivefs.py", line 466, in get_item_info

File "googledrive\\gdrivefs.py", line 241, in get_file_metadata

File "C:\\Program Files (x86)\\FME\\python\\requests\\sessions.py", line 546, in get

return self.request('GET', url, **kwargs)

File "googledrive\\gdrivefs.py", line 485, in request

File "fmegeneral\\fmehttp.py", line 318, in request

File "C:\\Program Files (x86)\\FME\\python\\pypac\\api.py", line 241, in request

raise request_exc # In PY2, just saying 'raise' may re-raise ProxyConfigExhaustedError.

File "C:\\Program Files (x86)\\FME\\python\\pypac\\api.py", line 230, in request

response = super(PACSession, self).request(method, url, proxies=proxies, **kwargs)

File "C:\\Program Files (x86)\\FME\\python\\requests\\sessions.py", line 519, in request

prep = self.prepare_request(req)

File "C:\\Program Files (x86)\\FME\\python\\requests\\sessions.py", line 452, in prepare_request

p.prepare(

File "C:\\Program Files (x86)\\FME\\python\\requests\\models.py", line 317, in prepare

self.prepare_auth(auth, url)

File "C:\\Program Files (x86)\\FME\\python\\requests\\models.py", line 548, in prepare_auth

r = auth(self)

File "fmegeneral\\webservices.py", line 169, in __call__

File "fmegeneral\\webservices.py", line 101, in get_authorization_header

fmewebservices.FMEWSException: Type: 3, Number: 1, Message: Failed to get authorization header.

2023-06-01 15:11:03| 0.9| 0.0|ERROR |Error encountered while calling method `input'

2023-06-01 15:11:03| 0.9| 0.0|FATAL |GoogleDriveConnector_CALLER (PythonFactory): PythonFactory failed to process feature

Hello @lferg​,

Google shutdown the use of the special redirect URI `urn:ietf:wg:oauth:2.0:oob` on October 3, 2022. This was the redirect URI used in Google-related web service templates in FME 2021 and older.

 

Safe updated the redirect URI (to https://localhost) for any affected web service templates for FME 2022 releases. However, older releases such as 2021 still uses the defunct redirect URI. Are you using an older version of FME and are you able to upgrade to FME 2022 and newer?

Thank you Debbiatsafe. I did wonder if it was a version issue. I'm running FME 2021.2.6 but will look at installing 2022

Thank you Debbiatsafe. I did wonder if it was a version issue. I'm running FME 2021.2.6 but will look at installing 2022

You're very welcome! I just want to add it is possible to continue using FME 2021 if the Google Drive web service template is updated to use the new redirect URL.

 

It involves making a copy of the web service template, updating the copy, and deleting the old template, and then renaming the copied template. You would also have to perform these steps for each Google-related service you plan to use. I can share more detailed steps if interested.

You're very welcome! I just want to add it is possible to continue using FME 2021 if the Google Drive web service template is updated to use the new redirect URL.

 

It involves making a copy of the web service template, updating the copy, and deleting the old template, and then renaming the copied template. You would also have to perform these steps for each Google-related service you plan to use. I can share more detailed steps if interested.

Debbi,

Definitely interested if you are able to share more detailed steps as to upgrade to 2022 I will have to also check that it is compatible with ArcMap 10.8.2

You're very welcome! I just want to add it is possible to continue using FME 2021 if the Google Drive web service template is updated to use the new redirect URL.

 

It involves making a copy of the web service template, updating the copy, and deleting the old template, and then renaming the copied template. You would also have to perform these steps for each Google-related service you plan to use. I can share more detailed steps if interested.

Hello @lferg​ 

Here are the steps to create an updated version of the web service template:

1) Open the Web Services dialog in Tools > FME Options > Web Connections. Select Manage Services (step a), click on the + dropdown (step b), choose Create From (step c), and select the Google Drive option (step d) to create a copy.

Steps to create Web Service Template copy2) Set an appropriate name for the template (eg. Google Drive Updated 2021) and manually change the Redirect URI field to: https://localhost. All other parameters can stay the same. Apply the changes and exit from the Web Connections dialog.

3) Using a GoogleDriveConnector transformer, select the Add Web Connection... option under the Google Drive Account parameter.

4) Click on the Web Service dropdown and select the updated template (eg. Google Drive Updated 2021) and select Authenticate. Proceed as usual to authenticate with Google Drive.

 

Once this has been done, a new Google Drive web connection should be created using an updated Google Drive web service template definition in FME 2021. I hope this helps.

Reply


Community Stats

30,162
Posts
114,483
Replies
37,809
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.