• Jake Handy
  • NEWBIE
  • 0 Points
  • Member since 2017

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 1
    Replies
Hi! I'm running into some authentication issues when trying to connect SharePoint as an external object and was curious if anyone had a solution. I’ve gone though the necessary steps to connect our SharePoint data to sales force but am running into this problem at the final step:

1. Login
2. Go to the Files tab
3. Click on "SharePoint Online" in Connected Sources (I set this up previously)
4. Click on "Connect to Microsoft SharePoint Online"

At this point, it brings up SharePoint which says “Do you trust Salesforce?”

5. Hit “Trust It” on this dialogue.

And then I’m routed back to Salesforce where it displays his error:

We can’t log you in because of the following error. For more information, contact your Salesforce administrator.
No_Oauth_Token: invalid_request AADSTS90014: The request body must contain the following parameter: 'resource'.Trace ID: f2d3c714-f1c3-4934-a04d-e3771bd62300Correlation ID: 9d8825a3-bd03-4674-a431-0229ff5ed2aaTimestamp: 2017-11-09 15:19:22Z
Hi! I'm running into some authentication issues when trying to connect SharePoint as an external object and was curious if anyone had a solution. I’ve gone though the necessary steps to connect our SharePoint data to sales force but am running into this problem at the final step:

1. Login
2. Go to the Files tab
3. Click on "SharePoint Online" in Connected Sources (I set this up previously)
4. Click on "Connect to Microsoft SharePoint Online"

At this point, it brings up SharePoint which says “Do you trust Salesforce?”

5. Hit “Trust It” on this dialogue.

And then I’m routed back to Salesforce where it displays his error:

We can’t log you in because of the following error. For more information, contact your Salesforce administrator.
No_Oauth_Token: invalid_request AADSTS90014: The request body must contain the following parameter: 'resource'.Trace ID: f2d3c714-f1c3-4934-a04d-e3771bd62300Correlation ID: 9d8825a3-bd03-4674-a431-0229ff5ed2aaTimestamp: 2017-11-09 15:19:22Z