Skip to main content
  • EN

Hi All, im having the issue of my ArcGIS readers and writers on my FME server (cloud 2021) expiring after a couple of weeks and needing manual re authentication.

What is the suggested work flow to automate authentication in FME Server to AGOL?

I have read all the forum posts about expiring tokens, watched a range of youtube videos, added client IDs, client secrets and FME server redirects but no luck, i have tried the FME desktop - Arcgis_Token_Getter Transformer. i can get a token but not sure where to put it....

 

My requirements are - From FME server 2021 read or write a ESRI arcgis online feature service and not to have to manually re-authenticate every two weeks? All my Desktop workspaces work fine (because I'm manually authenticating when I add the AGOL reader or writer) once I publish the workspace to server I have to wait 2 weeks to 'test' if it fails when the token expires so it takes me two weeks it iterate over my failure...

 

Does anyone have a workflow they could possibly share with me?? many pleases and thanks you's .

 

Steve

Hi ​@goatboyboz ,

A very late reply from my side since I've got a similar issue right now. Did you check this ticket? 

The problem seems to be solved if you run the workspace at least once every two weeks. 

 

But, unfortunately, this solution does not always work. Recently, suddenly all my esri web connections tokens were not valid any more. I guess all from the same moment on, but I'm not completely sure about this. I use arcgis online for multiple customers with multiple user accounts. All workspaces using these accounts suddenly resulted in errors about expired tokens. ​@siennaatsafe , since you seem to know more about this, do you have any idea why this is happening? Besides that, every now and then I have to renew some of the connections in fme flow. But this was the first time I had to renew them all at once. (And of course all of them in the middle of my holiday). It would be great if the connection/token can be refreshed automatically.

Hi ​@koenterralytics, 
 

Thanks for sharing your experience. It must have been really frustrating for all your connections to expire at once, especially while you were away. I’ve added your comments to our internal tracking under ticket FMEFLOW-17415.

Right now, this seems to be a relatively rare issue with OAuth services. ArcGIS Online is somewhat unique in that it enforces a short default refresh token expiry (2 weeks) and allows organizations to shorten it further, which makes unexpected expiry more likely. Addressing this would require significant changes to how we handle OAuth across FME, so for now it continues to be managed at the format level rather than within FME Flow itself. Because of that, this item isn’t currently prioritized for development.

That said, I’d recommend raising this as an Idea on the Community. Gathering feedback from other users will help us better understand how widespread this is. If more customers encounter the same issue, it will strengthen the case for a more permanent solution.

Kind regards,
Sienna

Community Stats

31,991
Posts
121,490
Replies
39,599
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.