I have a requirement that my Webhook Automation can only be triggered by authorized applications, so it would be great if Automations Webhooks supported authentication through header specification. Eg. The request to the Webhook requires an Authorization header key with an FME Server token similar to the FME Server REST 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.
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.
This would be a valuable add-on to the FME product for our organization. Although Workspace Webhooks have Authorization header enforcement, I have been unable to pass published parameter values into the workspace in this way. Therefore I would like Webhook Automation to introduce support for Authorization header authentication.
+15- Safer
https://docs.safe.com/fme/html/FME-Flow/WebUI/Automations-Triggers/Trigger-Webhook.htm
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.