Solved

FME 2023.2 Publish Failed (Not Authorized)

  • 15 December 2023
  • 2 replies
  • 88 views
warrendev
Rank
Badge +21

After upgrading to FME Flow and Form 2023.2 (Build 23764), I'm receiving errors publishing workspaces to FME Flow. Even when testing with the superuser credentials, I receive an error message. Has anyone else experienced this issue or have a workaround?

 

Steps Taken to Resolve

  • Reinstall FME Form
  • Reinstall FME Flow
  • Recreate FME Flow Connections

Error Message

image

2023-12-15 11:27:10|      |     |INFORM|Starting connection to '<redacted> FME Flow'
2023-12-15 11:27:10|      |     |INFORM|Connecting to 'https://<redacted>' (web connection, authenticated login)...
2023-12-15 11:27:10|      |     |INFORM|Successfully connected to FME Flow 2023.2 (build 23764).
2023-12-15 11:27:12|      |     |INFORM|Connecting to 'https://<redacted>' (web connection, authenticated login)...
2023-12-15 11:27:12|      |     |INFORM|Successfully connected to FME Flow 2023.2 (build 23764).
2023-12-15 11:27:20|      |     |INFORM|Retrieving service properties...
2023-12-15 11:27:20|      |     |INFORM|Successfully retrieved service properties.
2023-12-15 11:27:20|      |     |INFORM|Retrieving service parameters for '<redacted>.fmw'...
2023-12-15 11:27:20|      |     |INFORM|No service parameters found.
2023-12-15 11:27:22|      |     |INFORM|Uploading as '<redacted>.fmw'...
2023-12-15 11:27:23|      |     |ERROR |Publish failed (Not Authorized) - Ensure that credentials are correct, and that user has sufficient privileges.

 

icon

Best answer by warrendev 21 December 2023, 02:07

View original

2 replies

merlinegeorge
Rank
Badge +5

Hello,

 

Are you seeing this issue for all workspaces or specific workspaces in certain repositories on Flow?

 

You mentioned that you are publishing as superuser. Is it FME Flow's default superuser account or another superuser account? On the User Permissions in the Web UI, if you look at the user, do they have publish permissions to the repositories? Is this a system user or an AD/LDAP/SAML imported user ? Are you able to manually login to the FME FLow Web UI directly as that user ?

 

On the same machine as FME Server, can you try connecting from workbench with the web connection set to be http://localhost:port - any difference?

 

Did the machine host name change with the upgrade to FME Server? Are you using a proxy?

 

In case backup and restore process was performed, do you have anything logged under Backup & Restore > History from when you did the restore on the upgrade? Is there anything suspicious looking in the logs?

warrendev
Rank
Badge +21

Hello,

 

Are you seeing this issue for all workspaces or specific workspaces in certain repositories on Flow?

 

You mentioned that you are publishing as superuser. Is it FME Flow's default superuser account or another superuser account? On the User Permissions in the Web UI, if you look at the user, do they have publish permissions to the repositories? Is this a system user or an AD/LDAP/SAML imported user ? Are you able to manually login to the FME FLow Web UI directly as that user ?

 

On the same machine as FME Server, can you try connecting from workbench with the web connection set to be http://localhost:port - any difference?

 

Did the machine host name change with the upgrade to FME Server? Are you using a proxy?

 

In case backup and restore process was performed, do you have anything logged under Backup & Restore > History from when you did the restore on the upgrade? Is there anything suspicious looking in the logs?

Hi @Merline George​ ,

I'm hosting FME Flow in Azure which is behind an application gateway, and I believe it is related to the WAF. In testing, after setting the policy for "Inspect Request Body" to False, the errors no longer happen. I will work with our IT team to identify what is causing the issues.

Thank you for the help!

Chris

Reply


Community Stats

29,355
Posts
111,609
Replies
37,018
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.