Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      


Updated on February 9, 2022

The MasterCom Claims manager uses the OAuth protocol (version 1.0a) for secure authorization with the Google Body Hash Extension by using RSA for private key signing and SHA-256 as the hashing algorithm.

The GetMCOMAuthHeader function generates the request authorization header and handles message signing. The authorization header is generated by the SetAuthHeader data transform as part of the MCOMClaimsMgrRequestPostProcessing request post-processing data transform.

The logic of the SetAuthHeader data transform is defined as follows:

  • Get the JSON-formatted payload.
  • Build the parameters required to call the GetMCOMAuthHeader function.
  • Invoke the GetMCOMAuthHeader function.

The DeReferenceMCOMEndPoint activity dereferences the end point URL.

Sample authorization header

The following is a sample of an authorization header generated by the SetAuthHeader data transform:

Authorization: OAuth oauth_body_hash="5L%2F9PCnJnlKWZGh9sYPdOanyBJlp6t8VolyenPhW8sI%3D", 
oauth_consumer_key="your%20consumer%20key", oauth_nonce="s579vd4tdut3jdo2tajhqhbggh", 
oauth_signature_method="RSA-SHA256", oauth_timestamp="1523360492", oauth_version="1.0"


Smart Dispute for Issuers 7.4 - 7.48 Smart Dispute for Issuers Low-Code App Development Financial Services

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us