Skip to main content
  • EN

I am probably missing something really simple here, so I am looking at this example:

https://community.safe.com/s/article/streaming-geojson-with-fme-server-2016

 

I create a webhook, which gets me the URL and token.

 

So I then try to use a httpcaller from FME desktop to call that webhook, and pull down the data, but just putting this url in the httpcaller

 

https://myfmeserver/fmedatastreaming/testing/GeoJson.fmw?FEATURE_TYPES=Default.BusRoutes&token=f57z2802-4a5f-edcb-87fa-16c849facdce

 

But I get 401 unauthorized, is that not a valid syntax for adding the token to the URL? I also tried adding in the header dialog boxes, got the same.

 

 

The value you're entering there doesn't look like a token. A token should be 40 characters long with no dashes. It looks like you might be using the GUID of the token.

 

See wome more details here on how to set the token in calls

https://playground.fmeserver.com/using-the-rest-api/basics/

The value you're entering there doesn't look like a token. A token should be 40 characters long with no dashes. It looks like you might be using the GUID of the token.

 

See wome more details here on how to set the token in calls

https://playground.fmeserver.com/using-the-rest-api/basics/

When you gnerate a webhook, FME creates a token on the fly, and it does have dashes, when I look under tokens in FME server, I see it listed as a "Session token", it seems those have dashes. When I manully generate a token, it is does not have the dashes, but I get the same 401 unauthorized error with that as well.

So the syntax does work with the token (with the dashes) in the httpcaller, as long as I do not use the GET command, so apparently, that is not supported.

Reply


Community Stats

30,352
Posts
115,344
Replies
38,087
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.