@David_MA I appreciate your efforts to help with this. I will add some detail to make my question clearer.
My original question did not include a screenshot of the trigger of the flow I am trying to trigger. The screenshots show steps from another flow that I'm trying use to call the flow with the HTTP trigger from.
I.e. when I Run Flow 1 -> send an HTTP Request to Flow 2 with HTTP Trigger
For completeness, here is the trigger I am trying to trigger from another flow. It's currently set to be triggerable by 'Anyone' but I want to set it to 'Specific users in my tenant'
As you can see, you can select 'anyone' which allows anyone with the flow URL and signature key to trigger the flow by simply calling the URL. I don't want to select that as it's not as secure as I need it to be.
The question I'm asking is how you trigger this from another flow, when you select 'specific users in my tenant' since that requires authentication
I can't find anywhere that explains how to do that in simple terms.
The only place I've found that goes into any detail is here: Add OAuth authentication for HTTP request triggers - Power Automate | Microsoft Learn and I'm left with more questions than answers, since it doesn't seem to be geared around triggering one flow with the HTTP trigger from another flow with a HTTP request step.
Especially around the following 'claims' that need including in the request from Flow 1 to the Trigger of flow 2:
- "iss": <Issuer of the requestor>
What should this be set to?
Secondly, where in my HTTP request in Flow 1 should the claims be specified in order to successfully trigger the HTTP trigger of Flow 2?
Using some simplified examples to fill in for Flow 1 and Flow 2:
Flow 2 Using the HTTP Trigger
If I try to call Flow 2 from Flow 1 I get the following error:
Flow 1 using a HTTP Request to Trigger Flow 2
{
"error": {
"code": "DirectApiAuthorizationRequired",
"message": "The OAuth authorization scheme is required. Please add authentication scheme and try again."
}
}
I can change my HTTP request to use Active Directory OAuth:
But in that case what should be specified as the Client ID and Client Secret? Is the secret a static value and how do I find out what this is? This seems insecure.
Given it seems to be trying to use Azure AD for Authentication, it seems it should be possible to trigger the trigger using an 'Invoke HTTP Request with Azure AD' step, which would then add a connection using my credentials to the flow without having to explicitly state a secret - which seems like a more secure and simpler option.
However, if it's possible to trigger the http trigger this way - what should be specified as the Base URL and Azure AD Resource URI in the connection settings? As you can see in my original question, I've tied various values here but failed.
