Question
Evoke Technologies
US
Last activity: 23 Apr 2024 9:25 EDT
SharePoint Integration with Component
We setted up the SP Component and configured the Authentication Profile and Whatever required for Integration,
Now, While running one of the data pages D_SPOnlineCreateFolder, can see 403 HTTP Response Code. In the logs I see that an error occurs:
BEARER authentication error: No access token available
Also referring out this Authentication 403 error in SharePoint Online component but didn't get the exact context of it.
Thanks!
Accepted Solution
Updated: 23 Apr 2024 9:25 EDT
Pegasystems Inc.
GB
@AkshithReddyT the support ticket INC-B13496 was resolved with the following explanation
Issue with Market place product not in the scope of GCS support
https://community.pega.com/marketplace/integrations/sharepoint-online-integration .
The data page D_SPOnlineCreateFolder uses the same authentication profile used by rest of the data pages as part of sharepoint component. If customer is able to configure the authentication profile properly as pat of setup, then the only reason for this data page to fail is lack of access to specific folder under which new folder is being created.
What was confirmed was that client was able to generate the valid access token using the authentication profile, but not able to integrate the SharePoint. You were able to successfully Integrate with SharePoint from MSGraphAPI therefor involvement with client IT team and microsoft would be required to validate access to the specific folder.
Issue primary reason description:
We sett up the SP Component and configured the Authentication Profile and Whatever required for Integration,
Now, While running one of the data pages D_SPOnlineCreateFolder, can see 403 HTTP Response Code. In the logs I see that an error occurs:
@AkshithReddyT the support ticket INC-B13496 was resolved with the following explanation
Issue with Market place product not in the scope of GCS support
https://community.pega.com/marketplace/integrations/sharepoint-online-integration .
The data page D_SPOnlineCreateFolder uses the same authentication profile used by rest of the data pages as part of sharepoint component. If customer is able to configure the authentication profile properly as pat of setup, then the only reason for this data page to fail is lack of access to specific folder under which new folder is being created.
What was confirmed was that client was able to generate the valid access token using the authentication profile, but not able to integrate the SharePoint. You were able to successfully Integrate with SharePoint from MSGraphAPI therefor involvement with client IT team and microsoft would be required to validate access to the specific folder.
Issue primary reason description:
We sett up the SP Component and configured the Authentication Profile and Whatever required for Integration,
Now, While running one of the data pages D_SPOnlineCreateFolder, can see 403 HTTP Response Code. In the logs I see that an error occurs:
BEARER authentication error: No access token available Explanation description:
user was able to successfully Integrate with SharePoint from MSGraphAPI
Pegasystems Inc.
GB
@AkshithReddyT which SP Component are you referring to? Are you referring to the MarketPlace component as referenced here?
@nvkap could you comment on this question about SharePoint integration?
Please log a support ticket if you need further help.
Evoke Technologies
US
@MarijeSchillern Yes, its the one, https://community.pega.com/marketplace/integrations/sharepoint-online-integration?
and logged a support ticket INC-B13496
Accepted Solution
Updated: 23 Apr 2024 9:25 EDT
Pegasystems Inc.
GB
@AkshithReddyT the support ticket INC-B13496 was resolved with the following explanation
Issue with Market place product not in the scope of GCS support
https://community.pega.com/marketplace/integrations/sharepoint-online-integration .
The data page D_SPOnlineCreateFolder uses the same authentication profile used by rest of the data pages as part of sharepoint component. If customer is able to configure the authentication profile properly as pat of setup, then the only reason for this data page to fail is lack of access to specific folder under which new folder is being created.
What was confirmed was that client was able to generate the valid access token using the authentication profile, but not able to integrate the SharePoint. You were able to successfully Integrate with SharePoint from MSGraphAPI therefor involvement with client IT team and microsoft would be required to validate access to the specific folder.
Issue primary reason description:
We sett up the SP Component and configured the Authentication Profile and Whatever required for Integration,
Now, While running one of the data pages D_SPOnlineCreateFolder, can see 403 HTTP Response Code. In the logs I see that an error occurs:
@AkshithReddyT the support ticket INC-B13496 was resolved with the following explanation
Issue with Market place product not in the scope of GCS support
https://community.pega.com/marketplace/integrations/sharepoint-online-integration .
The data page D_SPOnlineCreateFolder uses the same authentication profile used by rest of the data pages as part of sharepoint component. If customer is able to configure the authentication profile properly as pat of setup, then the only reason for this data page to fail is lack of access to specific folder under which new folder is being created.
What was confirmed was that client was able to generate the valid access token using the authentication profile, but not able to integrate the SharePoint. You were able to successfully Integrate with SharePoint from MSGraphAPI therefor involvement with client IT team and microsoft would be required to validate access to the specific folder.
Issue primary reason description:
We sett up the SP Component and configured the Authentication Profile and Whatever required for Integration,
Now, While running one of the data pages D_SPOnlineCreateFolder, can see 403 HTTP Response Code. In the logs I see that an error occurs:
BEARER authentication error: No access token available Explanation description:
user was able to successfully Integrate with SharePoint from MSGraphAPI