Skip to main content

We have an integration running that leverages named credential to access a hosted app in the Microsoft cloud (graph api).  Auth provider in SF is Microsoft Access Control Service. The application works with no issues if Microsoft's conditional access is disabled.  If it is enabled, however, the oauth token request process stops before it can complete.  This appears to be the result of a challenge sent from Microsoft instead of the token per the following article: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-conditional-access-dev-guide

Does the Salesforce oauth implementation or custom auth provider provide a mechanism to catch this challenge and handle it with potentially additional user interaction?  Can we leverage custom auth provider to accomplish the flow outlined in the article?

3 Antworten
  1. 15. März 2022, 17:24

    BTW, we are testing that the endpoint (Windows 10/11 in this case) is managed and it looks like the metadata for this is missing when Azure gets the request, even though we are using Edge.

0/9000