How to get Access Token in FSM for OAuth2.0 through configuration? for Azure

Hi @Damodaran ,

Please refer below steps to setup your OAuth2.0 ExtractHandler. (Source from R&D)

In the example, we are going to send a request to "https://graph.microsoft.com/v1.0/users" REST service, to create a user which has a display name mapped to the FSM person_id, using an access token acquired through the OAuth2ExtractHandler.

Create a XML map for the outbound integration
-------------------------------------------------
1. From main menu select XML Maps screen.
2. For the map name give any name
3. Check "Allow Export" and "Allow Import" check boxes.
4. For the primary table select Person table, for primary path set //person.
5. In the Details tab - uncheck "Extract XML Declaration".
6. In the Mapping tab, for FSM column name set "PERSON_ID", for extract column name set "displayName". (according to the example)
7. Save and refresh integration cache.

Create integration message routing rule.
-------------------------------------------
1. For the Rule ID set any name.
2. For Routing Type select - "Send Message".
3. For the Handler select - "Metrix.Integration.Handlers.OAuth2ExtractHandler".
4. For the Dataconnector select - "Metrix.Integration.JSONOutboundConnector".
5. For the Map ID select the outbound map that we have defined earlier.
6. Save screen and it will populate with routing arguments.

7. For "AccessTokenURL" set the token endpoint URL 

8. For "AuthenticationMode" set "Bearer".
9. For "ClientId" set value of app param OPENID_WEB_APPLICATION_ID.
10. For "ClientSecret" set value of app param OPENID_SECRET.
11. For "HTTPHeaders" set "Content-Type: application/json"
12. For "HTTPMethod" set "POST".
13. For "Scope" set "https://graph.microsoft.com/.default".
14. For "URL" set "https://graph.microsoft.com/v1.0/users".
15. Save and verify that AccessTokenURL, ClientId and ClientSecret arguments are encrypted.
16. Refresh integration cache.

16. In XML poster send below message.

<perform_outbound_integration>
<parameters>
<dataconnector>Metrix.Integration.JSONOutboundConnector</dataconnector>
<extract_entity>YOUR_MAP</extract_entity>
<message_name>
</message_name>
<enable_time_constrain>N</enable_time_constrain>
<input>
<primary_table_constraints>
<person_id>ADMIN</person_id>
</primary_table_constraints>
</input>
</parameters>
</perform_outbound_integration>

17. Check for a response similar to the below response with error message - "The remote server returned an error: (400) Bad Request."

<perform_outbound_integration_result>
<response>Transaction Complete.</response>
<run_id>187377</run_id>
<run_status>EXCEPTION</run_status>
<run_message>The remote server returned an error: (400) Bad Request.</run_message>
</perform_outbound_integration_result>

18. Go to the relevant run id and check the "Transaction Result" field. It will show an error message - "no expected type is available" as the reason for the 404 Bad Request error.
19. From routing rule "ClientSecret" change the client secret, save it and refresh integration cache.
20. Resend the XML message and check for the error message - "AccessToken is required for bearer authentication."
 

Note:

Reason for the "The remote server returned an error: (400) Bad Request." error message when testing the outbound integration using "JSONOutboundConnector" is, when converting the mapped xml to JSON, "JSONOutboundConnector" does not omit the root element name.

Therefore the graph api receives a request which has content like below,
{
"person":

{ "displayName": "ADMIN" }

However, the expected request content for the POST request (to create a user) is,

{ "displayName": "ADMIN" }