@siennaatsafe from memory you looked into this. Thanks.

Hi @dkirouac,

This is the expected behavior. Previously, the ArcGIS Online refresh tokens would last forever. The refresh token is used to get the short-lasting access token with each connection. This was recently changed so now refresh tokens expire.

With our current system, you'll have to manually refresh your connection to get a new refresh token. We've tried to fix this in 2019.2. So now, we automatically refresh the refresh tokens. Hopefully, this will prevent users from having to reauthenticate their connections. However, we've found this issue very hard to reproduce internally. So if you do have to manually re-authenticate in 2019.2 please let me know.

We've been working very hard to develop a seamless connection with ArcGIS Online. I've detailed all the issues and fixes I am aware of here https://knowledge.safe.com/articles/99956/arcgis-online-connection-troublshooting.html

If you have any questions please let me know.

Hi Sienna, We are encountering a similar issue using FMS Server build 19630 at a client connecting to their ArcGIS Online subscription. The connections work for approximately a month and then fail. To remedy we open FME Server and re-authenticate the connection and it continues to work as expected until the token expires again. Do you have a suggestion on how to remedy?

Hi @mikeleenz,

The token refresh was introduced in build 19796 and unfortunately, there is no workaround in FME other than manually refreshing the token after it expires. However, in the ArcGIS Online documentation, there may be a way for the user to set the refresh token. We haven't been able to track down where this is but it is in the documentation. https://developers.arcgis.com/rest/users-groups-and-items/authentication.htm

"The refresh token that's returned may be valid for a shorter period than requested based on the maximum expiry time set by the user's organization or the platform."

Perhaps it's possible to extend the refresh token.

Thanks Sienna,

Thanks Sienna,

We are in the process of upgrading to 2019.2 but we will not know the results for a few months when it normally times out.

Hi @mikeleenz,

Thanks for sharing that! I'll pass it onto the developers and see what they think. :)

Hi Sienna,

We're using FME Server 2019.2.3.2 Build 19825 - win64 and we still need to manually re-authenticate. Has there been any more progress on this topic?

Thanks!

We upgraded to build 19817 (2020.2.2) and have not had to refresh the token since March.

Hi @danielwebb,

We haven't updated anything since build 19806. How often are you using your AGOL connection? How often do you need to re-authorize your connection?

Hi @siennaatsafe​ , I'm using ArcGIS Portal Feature service Reader/Writer and I'm seeing similar behavior. The job runs on FME Server 2020. At the beginning of the month stops running, some kind of manual intervention occurred (I assume it was my colleague troubleshooting the issue and running the job manually) and the job had run successfully again for another 3-4 weeks.

Could you please confirm/deny this could be the case so I can rule out this as a possible cause?

Thank you

Hi @honkovam​ ,

It could be a similar issue. What authentication are you using in the ArcGIS Portal Feature service Reader/Writer? Are you using a web connection?

One thing you can try is extending the OAuth refresh token in your portal. https://enterprise.arcgis.com/en/portal/latest/administer/linux/specify-the-default-token-expiration-time.htm#:~:text=The%20default%20expiration%20time%20is,used%20until%20the%20token%20expires

Hi @siennaatsafe​,

I am using the Generate Token option as Authentication Type (ArcGIS Portal built in user).

Thank you

Hi @honkovam​ ,

Thank you for letting me know. I don't believe that this issue would affect you then. This issue is specifically an issue with an OAuth type of connection. The generate token, doesn't require a refresh token. It just gets a new access token each time.

You could try changing the expiry of your access tokens to see if that helps https://enterprise.arcgis.com/en/portal/latest/administer/linux/specify-the-default-token-expiration-time.htm#:~:text=The%20default%20expiration%20time%20is,used%20until%20the%20token%20expires

any updates on this?

unlike AGOL, portal does not seem to update token for oauth web connection. the current portal token expiration value is -1. I thought the mechanics for oauth web connection be the same between AGOL and Portal. we dont have issue with AGOL web connection being expire however web connection to portal fail to update token and requires manual re-authentication.

any ideas?

thanks in advance!

Portal 10.8.1

FME 2023.2

Hi @gistech_ ,

A lot of development work went into our portal and arcgis online authorization process so most if not all issues should be resolved. 

One issue we could not get around is if the connection is not used within two weeks the refresh token will expire. Even if it’s set to -1 in your portal, it will still expire. Is your connection being used at least one every two weeks?

If it is and you are still encountering issues. I’d open a support case with us. 

Kind regards, 

Sienna

Hi ​@siennaatsafe 

running it every 2 weeks appears solve the refresh issue for now, given the other requirements in place. Tnx for the advice!