• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 38 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 35810 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

Outlook Integration error

Ankur V

I am using connected system with Oauth2.0 to connect to office365 and get the calendars i m able to authorize using connected system however when testing the base url I get the below error

Invalid credentials

Appian was not able to authenticate with the access token you provided. This request requires Bearer authentication. HTTP/1.1 401 Unauthorized Next Steps

  • This integration is using a connected system with OAuth 2.0 authentication configured. You may need to authorize access to the external system and retry the request.
  • Make sure that you are using the correct OAuth 2.0 configuration for this external system
  • Make sure that the OAuth 2.0 configuration provides the required scope to make this request
  • Check the request and response for more details
  • Review the external systems documentation for information on what may have caused the problem

When i run the authorization its executes successfully.  Has any one seen this issue before or can someone share the Oauth2.0 configuration related to outlook ( For outlook defining a scope is mandatory)

  Discussion posts and replies are publicly visible

  • 0
    Appian Employee
    I have integrated Appian with Office 365 before using the OAuth 2.0 client credentials grant type. A few questions before I can give proper advice:

    What is the use case here?
    What APIs are you attempting to use?
    Do you want to call them as the user who is logged into Appian or do you want to use a service account?
    Do you have an app set up in Azure AD for this and if so how is it set up?

    All of these answers will help determine how to set this up in Appian. Also in speaking with Microsoft consultants, Microsoft Graph APIs should be used going forward instead of Office 365 APIs.
  • 0 in reply to Steven Miccile
    Use Case: Using appian to get users calendar from Outlook for OOO, busy schedule etc
    What APIs are you attempting to use? --- We are making a regular Web connection with implicit flow and a redirect url to appian
    Do you want to call them as the user who is logged into Appian or do you want to use a service account? -- For testing we would use user but for production deploy it would be a service account.
    Do you have an app set up in Azure AD for this and if so how is it set up? --- App is setup in Azure with client ID secret and required permission to read users calendars.
  • 0
    Appian Employee
     in reply to Ankur V

    You mention wanting to use the implicit grant flow, but Appian Connected System OAuth 2.0 in 18.3 supports authorization code grant flow. This could explain your issue.

    If you are planning on treating this integration like a service account, I recommend the client credentials grant type, which is designed for these scenarios. To do this in Appian 18.3 you can create two Appian Integration objects: one that requests the token and one that uses the token for the actual request. As announced during the 18.4 webinar, Appian will have a specific feature for client credentials grant type configuration in 18.4 as well.

    Also, I recommend moving towards Microsoft Graph REST APIs rather than Office 365 REST APIs. This is because when using the client credentials grant type with Office 365 REST APIs, Microsoft requires you to register an x509 cert with the application and sign API calls with it via a JWT. This is a pain to set up in Azure and requires a plugin in Appian. Meanwhile, Microsoft Graph APIs require none of that and are much easier to set up.

    The only reason my implementation had to do all this for Office 365 is because the "Find Meeting Times" API in Graph has a bug that has gone unfixed for years, while the "Find Meeting Times" API in Office 365 works fine. If you don't need that service, go with Graph!

  • 0 in reply to Steven Miccile
    Do i create Appian Integration objects one that requests the token and one that uses the token for the actual request as a expression rule i don't see a way to do this via integration option in the connected system.
  • +1
    Appian Employee
     in reply to Ankur V

    You have to build the details (url, parameters, body) of the 2 requests yourself. Integrations can be created outside connected systems so I recommend starting with that. For both of them you will select "None" for authentication since you will be configuring the token exchange yourself. This method below requests a new bearer token every call. You could also cache the token in the database for re-use, but we decided against that method in favor of this one to limit the exposure of where the token is accessible.

     

    Integration 1 - Getting the bearer token

    URL: https://login.microsoftonline.com/<INSERT_ORG_SPECIFIC_URL>/oauth2/v2.0/token

    Parameters: None

    Headers: None

    Body:

    "grant_type=client_credentials&
    scope=https%3A%2F%2Fgraph.microsoft.com%2F.default&
    client_id="&cons!YOUR_CLIENT_ID&"&
    client_secret="&cons!YOUR_CLIENT_SECRET

    make sure to lock down the security on these constants to admins only

     

    Integration 2 - Making a request using this token

    URL/parameters/body: This is whatever Graph REST API you are trying to use

    Headers: Authorization - "Bearer "&rule!MG_ws_getGraphBearerTokenQ().result.body.access_token

     

    In this case, rule!MG_ws_getGraphBearerTokenQ() is what we configured in "Integration 1"

  • 0 in reply to Steven Miccile
    Thanks will give this a try i hope this would work for SharePoint in 365 as well.
  • 0 in reply to Steven Miccile
    I am able to get to the Integration 1 can you share the expression rule example to achieve the Integration 2?
  • +1
    Appian Employee
     in reply to Ankur V

    The Integration details for #2 are completely dependent on what Graph REST API you are trying to call and the format that API expects. You will have to read the Graph API documentation. I showed you the headers section which is important because that is how you pass the token.

    But here is an example:

     

© 2024 Appian. All rights reserved.