Skip to main content
Solved

HTTP authentication behavior changes between 2022.1 and 2022.2 - additional configuration needed?

  • October 23, 2023
  • 3 replies
  • 41 views
willhwilson
Contributor
Forum|alt.badge.img+7

I have an FME workbench set up in Flow that grabs an XML file from an HTTP location - in that application the access is denied and no features are read. This same workspace when downloaded into a desktop workspace and when run with FME Form has no problem reading the XML into features and I can run the process successfully. What gives?

 

Edit - I noticed the client was using the FME Server 2022.2 but provided me with FME Desktop version 2022.1. I updated the FME Desktop version to 2022.2 and now the HTTP requests register 401 unauthorized in both applications so I think this is less about any issue between Form and Flow and more about some nuance between versions... I can still connect to HTTP just fine in 2022.1 on same machine, same creds in a variety of transformers\\readers - but in 2022.2 no dice. Something changed between point versions but do not see this in Issues documentation.

Best answer by willhwilson

Thanks Matt. I think i resolved this. The client had parameters in the schedule using http protocol that I overlooked. While the workspace utilized https protocol in the source path, the sequence of workspaces were using these outdated path strings in Server. Got rid of the schedule-level parameters and all is well.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+47

How are you authenticating the service? Are you using a web connection or some other authentication method?

 

You can try to turn on debug logging to see if there are any differences in there. Debug logging can be helpful with HTTP stuff as it gives a few more details.

willhwilson
Contributor
Forum|alt.badge.img+7
  • willhwilsonContributor
  • Author
  • Contributor
  • Best Answer
  • October 24, 2023

Thanks Matt. I think i resolved this. The client had parameters in the schedule using http protocol that I overlooked. While the workspace utilized https protocol in the source path, the sequence of workspaces were using these outdated path strings in Server. Got rid of the schedule-level parameters and all is well.

virtualcitymatt
Celebrity
Forum|alt.badge.img+47

Thanks Matt. I think i resolved this. The client had parameters in the schedule using http protocol that I overlooked. While the workspace utilized https protocol in the source path, the sequence of workspaces were using these outdated path strings in Server. Got rid of the schedule-level parameters and all is well.

Ahhh that old chestnut - great to hear that it's not a bug

Community Stats

32,120
Posts
121,954
Replies
39,772
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.