OriginalPostID-248086
Discussion posts and replies are publicly visible
Hi Chanakya Volam
I finally figured it out. I have included ?resource=https://mytenantname.sharepoint.com in https://login.microsoftonline.com/common/oauth2/authorize?resource=https://mytenantname.sharepoint.com(Authorization URL)and it worked like a charm. :)
Thank you very much!
Hi,
Great that you figured it out. I thought informed to include resource in URL even I use resource in the URL
Hi Alok, are you able to use the connected systems with oAuth2.0 on Sharepoint Online? We failed the last time we tried doing so. We are on v18.1c. Appian support told us the following:
"Our product team has investigated this integration pattern and found that Sharepoint Online uses a nonstandard implementation for its authentication. As such, the Sharepoint Online OAuth 2.0 authentication strategy is not compatible with the currently supported Appian OAuth 2.0 strategy.
Specifically, the product team found the following items:
- the resource parameter IS needed to be placed in the _body_ of the request, and Appian currently does not support arbitrary parameters being added to the body of the token request.
- the client ID must be in two different formats when it is first sent to the Authorization endpoint and then when it is sent to the Token endpoint. This is also not currently supported by Appian.
As such, I can raise a use case to have supported added for Sharepoint's particular authentication requirements, but the product does not support it at this stage. If you have the appropriate expertise on-site (or through a PS/partner engagement), its possible that you could perform the integration using a plugin."
Hi All,
Please refer to the document below for the solution. This approach uses Azure Active Directory for Authentication & Authorization and Appian OOTB functionality only.
Appian-SharePointOnline_Integration.docx