Connecting Office365 using OData Client connector : Browse object: Oops, an unexpected error has occurred

Document created by aarthi_sridhar Employee on Mar 12, 2018Last modified by sheng_liao462475 on Mar 14, 2018
Version 2Show Document
  • View in full screen mode

OData Client connector

Use the OData Client connector to connect AtomSphere with any OData service.  Many providers offer access to their data by using the OData protocol, including Microsoft Windows Azure. 

While connecting to Office365 using OData Client connector, make sure you are able to generate access token using OData client connector (OAuth 2.0 while using OAuth authentication type). When you try to use the same connection in OData client connector operation to get/import the objects from Office365 you might be getting the following error: 'Oops, an unexpected error has occurred. Boomi has been notified of the issue'. There can be 2 causes for which you are unable to browse the objects using this connection.

 

 

 

Cause 1:

There could be chances that the user in the connection has incorrect permissions or scope. You may end up getting error message in our platform logs as 

" Caused by: OAuthProblemException{error='invalid_grant', description='AADSTS65001: The user or administrator has not consented to use the application with ID '588aXXXXXa409-4efb-bdc8-eYYYYYY2f6dc2' named 'Boomi'. Send an interactive authorization request for this user and resource. " Fixing the right permissions would resolve the issue to browse objects in the operation if the Postman works and HTTP client connector works fine.  Your application has to be registered properly and settings in the registration should be configured properly. You may try for both "https://outlook.office.com/api/v2.0/" and "https://outlook.office.com" in Boomi. These will confirm that the connection is established. Removing the delegated permissions for user on the admin account and then re-enabling them might also help. There could be also that there were no sufficient privileges to get metadata hitting a live endpoint to pull back actual data. Below is the picture showcasing permissions provided to the user and connection, operations sample screenshots.


 

 

 

 

 

Cause 2: 

Adding an Authorization parameter in the connection (response_type:code), would also resolve the issue and enable to see the objects in operation. 

 

Useful links:  OData Clientconnector 

Attachments

    Outcomes