Skip to main content
Solved

REST API header token authorization fails on FME Server 2017

  • February 28, 2018
  • 3 replies
  • 33 views
D

On FME Server 2017 Rest API V3, the header token based authentication always fails. I am setting the header based on this documentation: https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html

For example:

curl -X GET -H "Content-type: application/json" -H "Accept: application/json"  \
-H "Authorization: fmetoken token=abc123456789"  \
'http://myfmeserver/fmedatastreaming/metering/meterping.fmw?meterid=123456' 

receives the following error: 

The request has not been applied because it lacks valid authentication credentials for the target resource.

But, using the token in a query param works:

curl -X GET -H "Content-type: application/json" -H "Accept: application/json"  \
'http://myfmeserver/fmedatastreaming/metering/meterping.fmw?meterid=123456&token;=abc123456789' 

Also basic auth with an Authorization header works:

curl -X GET -H "Content-type: application/json" -H "Accept: application/json"  \
-H "Authorization:  Basic mybase64digest="  \
'http://myfmeserver/fmedatastreaming/metering/meterping.fmw?meterid=123456' 

I checked CORS to make sure it was allowing Authorization headers, is there another configuration I need to check? Any help would be greatly appreciated!

Best answer by laurawatsafe

Hi @danielspence,

It looks like you're hitting a bit of a shortcoming in FME Server when running a job using a URL to one of the services that isn't technically part of the REST API. The authorization header will only work when sending a request to a url that includes http://myfmeserver/fmerest/v3/ at the beginning.

In this case, the call is going directly to the data streaming service instead which doesn't support the the authorization header at this time. You would see the same behaviour when running the job using fmejobsubmitter or fmedatadownload as well. The calls to run a job that do support the authorization header are the ones documented at http://myfmeserver/fmerest under Transformations.

We have a few requests being tracked internally for adding support for this to the data streaming and data download services in FME Server, but it doesn't look like we have any Ideas for this posted yet. Would you be willing to post this to the Ideas page (https://knowledge.safe.com/content/idea/list.html)? The more votes your idea gets, the more likely it will be completed sooner.

View original
Did this help you find an answer to your question?

3 replies

laurawatsafe
Safer
Forum|alt.badge.img+11
  • laurawatsafeSafer
  • Safer
  • Best Answer
  • March 1, 2018

Hi @danielspence,

It looks like you're hitting a bit of a shortcoming in FME Server when running a job using a URL to one of the services that isn't technically part of the REST API. The authorization header will only work when sending a request to a url that includes http://myfmeserver/fmerest/v3/ at the beginning.

In this case, the call is going directly to the data streaming service instead which doesn't support the the authorization header at this time. You would see the same behaviour when running the job using fmejobsubmitter or fmedatadownload as well. The calls to run a job that do support the authorization header are the ones documented at http://myfmeserver/fmerest under Transformations.

We have a few requests being tracked internally for adding support for this to the data streaming and data download services in FME Server, but it doesn't look like we have any Ideas for this posted yet. Would you be willing to post this to the Ideas page (https://knowledge.safe.com/content/idea/list.html)? The more votes your idea gets, the more likely it will be completed sooner.

D
lauraatsafe wrote:

Hi @danielspence,

It looks like you're hitting a bit of a shortcoming in FME Server when running a job using a URL to one of the services that isn't technically part of the REST API. The authorization header will only work when sending a request to a url that includes http://myfmeserver/fmerest/v3/ at the beginning.

In this case, the call is going directly to the data streaming service instead which doesn't support the the authorization header at this time. You would see the same behaviour when running the job using fmejobsubmitter or fmedatadownload as well. The calls to run a job that do support the authorization header are the ones documented at http://myfmeserver/fmerest under Transformations.

We have a few requests being tracked internally for adding support for this to the data streaming and data download services in FME Server, but it doesn't look like we have any Ideas for this posted yet. Would you be willing to post this to the Ideas page (https://knowledge.safe.com/content/idea/list.html)? The more votes your idea gets, the more likely it will be completed sooner.

Thank you, for some reason I thought they were covered under the transformations API. I created a new idea here: https://knowledge.safe.com/idea/65109/support-for-adding-authorization-header-token-supp.html

 

G
Forum|alt.badge.img
danielspence wrote:
Thank you, for some reason I thought they were covered under the transformations API. I created a new idea here: https://knowledge.safe.com/idea/65109/support-for-adding-authorization-header-token-supp.html

 

Hi @danielspence

 

Please check out this idea too. It suggests to invoke all services via the FME Server REST API which would solve your problem and make it easier to work with the services:

 

https://knowledge.safe.com/idea/55255/support-datadownload-datastreaming-in-the-fme-serv.html

 

Thanks!

 

Reply


Helpful Members This Week

Community Stats

30,894
Posts
117,084
Replies
38,701
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.