Skip to main content
Question

Form not connecting to FLOW using Azure OAuth

  • November 7, 2025
  • 1 reply
  • 46 views

chadprop
Contributor
Forum|alt.badge.img+2

Hi,
I have a unique situation where my org can’t connect to Flow from Form desktop.
Some background first.

We are hosting our own server with Flow 2025.0, and Form to match.
For several months now we have been using Microsoft Azure to login to Flow, and to also connect via Form using the same authentication method.  The Azure login to Flow via the web GUI still works without any issue.  Visiting the Manage Web Services options, the web service that was built using the MS Azure Active Directory template authenticates fine using the “Test” option so proper communication is occurring between the Microsoft tenant and our Flow server.

Our IT department recently upgraded the GIS team to Windows 11 and since then we’ve experienced problems.
Within Form, using the admin account with a password still works and we can carry on publishing.
However, trying to connect via Azure is giving us fits.   Any attempt to create a new connection to Flow results in the following error message - “Request to update access token in connection storage failed.  (HTTP Error ‘HTTP/1.1 500’)”
Using Fiddler to inspect the app traffic, it appears that both the calls to Flow and to Microsoft are going through but there is an HTTP 502 error connecting to localhost:443.
I’ve even tried getting the IT dept to update the local hosts file on my pc with a 127.0.0.1 to localhost mapping but the error message persists.

Has anyone else seen this behaviour, and if so how did you resolve it?

Update - have determined after additional testing that the local pc config is probably not to blame, so left with troubleshooting that needs to happen on the VM hosting FME Flow.

Cheers

Chad

1 reply

aaron.hillier
Safer
Forum|alt.badge.img+6
  • Safer
  • 6 replies
  • November 12, 2025

Hi ​@chadprop,

 

Sorry to hear that you’re experiencing this issue! This one may be better suited to a support ticket - in your ticket, could you please include your description above (along with any other potentially relevant information), as well as the following log files:

  • fmeserver.log (<FlowSystemShare>\resources\logs\core\current)
  • fmeoauth.log (<FlowSystemShare>\resources\logs\service\current)
  • localhost_access_log.txt (<FlowSystemShare>\resources\logs\tomcat)

 

Looking forward to helping you resolve this issue!

 

- Aaron H.