I'm following this tutorial for implementing on-behalf-of flow with Microsoft Identity Platform. Specifically, it mentions that in my backend server I should add my React app as a known client application in the manifest. I've done this and it seems to be working. But I also see in the Azure portal under "Expose an API" that I can add an "Authorized client application" and the description is "Authorizing a client application indicates that this API trusts the application and users should not be asked to consent when the client calls this API." This sounds very similar to the description for adding a known client application.
Adding a known client application to the manifest does not automatically add the same client as an Authorized client, so I'm led to believe they are separate things. Can anyone shed light on the differences?
In single tenant scenario, if the
ClientAppis added as Authorized client applications, then the user will be able to directly login without providing any consent when theServerAppAPI is called by theClientApp:I used the below endpoint to authorize user and user is directly logged in without providing consent:
You can update the known client application in the manifest like below:
References:
Authorized client applications by Joy Wang
Known client applications by JoonasW