Skip to main content
  • Home
  • Ideas
  • Support for adding authorization header token support directly to services
Released

Support for adding authorization header token support directly to services

Related products:FME Form
  • March 1, 2018
  • 1 reply
  • 5 views
D

Adding authorization header token support to data streaming, job submitter, data download services. Possibly by aligning or incorporating them into the REST API via the transformations api.

For example:

POST /transformations/submit | transact | transactadata/<service>/< repository >/< workspace >

Or maybe through a new Services Manager API?

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

1 reply

rylanatsafe
Safer
Forum|alt.badge.img+13
  • rylanatsafeSafer
  • Safer
  • November 7, 2019

I am happy to note that as of FME Server 2018.0 (Build 18267) and 2018.1 (Build 18415), we have supported tokens in the Authorization header.

HeaderValueAuthorization

 

fmetoken token=<token>

 

 

For those of you running newer versions of FME Server – you will notice we provide this documentation when going through the 'Create Webhook' workflow.

Authorization with Header is documented in FME Server'

 

Helpful Members This Week

Community Stats

30,906
Posts
117,104
Replies
38,707
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.