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.
Released
Automations Webhook Authentication
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.
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.
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.
+18- Safer
https://docs.safe.com/fme/html/FME-Flow/WebUI/Automations-Triggers/Trigger-Webhook.htm