OriginalPostID-248086
Discussion posts and replies are publicly visible
Hi,
I was able to authenticate but no refresh token is captured. Also, when I use the Connected System in Integration, I am getting 403. Please see the images below.
Hi, So the Authorization Endpoint and Token Request Endpoint seems to be different then what I usually use. We use Authorization Endpoint as following login.microsoftonline.com/xxxxxxx/oauth2/authorize URI trying to access" XXXXXXXXXX is the resource id of the sharepoint which can be accessed from Azure and Token Endpoint is as following login.microsoftonline.com/xxxxxxxx/oauth2/token XXXXXXXX is the same resource id used in the auth endpoint. Hope this helps
Hi Chanakya Volam (chanakyav0001),
I am getting the below error.
Btw, I have registered Appian as a SharePoint Add-In.
Hi Arun,
You can follow below mentioned steps to identify / resolve this issue:
Hope you will be able to trace out the root cause of this failure.
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."