Question

4
Replies
382
Views
Giri Konatham (GiriKonatham)
Kelly Services
Sr. Consultant - BPM
Kelly Services
US
GiriKonatham Member since 2008 17 posts
Kelly Services
Posted: January 9, 2021
Last activity: May 16, 2021
Posted: 9 Jan 2021 19:10 EST
Last activity: 16 May 2021 13:39 EDT
Solved

Email Account Using Microsoft Graph As Receiver With Office 365 Email Provider In 8.4.3 Doesn't Work

Hello All,

Our organization is migrating from the IMAP (using user name and password) approach to Microsoft Graph with Office 365 using OAUTH 2.0.

Hence, my application built on PegaRules 8.4.3 Cloud, has to upgrade all the current email account rules that were configured with IMAP (using user name and password) to Microsoft Graph with Office 365 email provider using OAUTH 2.0.

We came to know from the help that Pega is limiting the grant type of the OAUTH profile to either Client Credentials or Password Credentials. Clearly we cannot use the Password credentials as this is what our organization messaging team are deprecating, hence the only option left for us it to set up the OAUTH 2.0 profile with Client credentials.

Hence, we started this migration procedure with the help of messaging team and we have created the new OAUTH 2.0 profile with grant type as Client credentials. 

We have configured OAUTH2.0 profile as below:

Hello All,

Our organization is migrating from the IMAP (using user name and password) approach to Microsoft Graph with Office 365 using OAUTH 2.0.

Hence, my application built on PegaRules 8.4.3 Cloud, has to upgrade all the current email account rules that were configured with IMAP (using user name and password) to Microsoft Graph with Office 365 email provider using OAUTH 2.0.

We came to know from the help that Pega is limiting the grant type of the OAUTH profile to either Client Credentials or Password Credentials. Clearly we cannot use the Password credentials as this is what our organization messaging team are deprecating, hence the only option left for us it to set up the OAUTH 2.0 profile with Client credentials.

Hence, we started this migration procedure with the help of messaging team and we have created the new OAUTH 2.0 profile with grant type as Client credentials. 

We have configured OAUTH2.0 profile as below:

  1. Client Identifier = Messaging team provided by creating app in their Azure
  2. Client Secrete   = Messaging team provided by creating app in their Azure 
  3. Scope = https://graph.microsoft.com/.default (this is mandatory, without this, we cannot establish connection, and the value is generic provided by Microsoft)
  4. Access token end point URL = https://login.microsoftonline.com/organizations/oauth2/v2.0/token  (this is mandatory, without this, we cannot establish connection, and the value is generic provided by Microsoft)

 

Now, when we tested our connection from email account rule using "Test Connectivity" in the receiver section, then we get the exception which is attached as a screen shot.

Response code 401, Unauthorized Handling error response Deserializing type GraphErrorResponse Graph service exception Error code: NoPermissionsInAccessToken Error message: The token contains no permissions, or permissions can not be understood.

 

We tried the same in postman tool and get the same error.

When messaging team tries to get Microsoft support teams help, they claimed that they cannot configure an app in Azure without a re-direct URL.

Which is available only if OAUTH2.0 profile is configured with grant type as "Authorization code, which is limited when Microsoft Graph is selected via email account rule.

Now, we are kind of in a confusion state and kind of stuck here and neither team (Pega or Messaging team) know how to resolve this issue.

If this feature was provided by Pega, then 

  1. How they tested this?
  2. Are we missing any permissions or configuration setting either from app or cloud perspective?
  3. Did anyone implemented Microsoft Graph option from email account?

Any assistance or hint here is much appreciated.

 

 

Pega Platform 8.4.3 Case Management Cloud Services Pega Cloud Conversational Channels Decision Management Other Industry Lead System Architect Support Case Exists