Power Platform Community Forum Thread Details

Hi,

I've come across a number of articles which mention using the Relative Path as a way to secure the HTTP Request Received trigger, e.g. More Securely Access an HTTP Request Trigger - Barret Codes (barretblake.dev), Securing your HTTP triggered flow in Power Automate – Stefano Demiliani

However, when trying to access to path parameter using the dynamic content option, it is prepended with 'Header' - which differs from the article graphics explaining this process

when accessing the 'Headers SecurityToken' output from the 'http request received' trigger, as shown above, it is empty. Has anyone else encounter this and/or found a fix?

I'm using a workaround and passing the token via query parameter instead, but wondering if the above is an issue here or a bug with the trigger

Also, are we still unable to use the schema validation in the settings on the HTTP Request Received Trigger? When enabled the flow errors on save