Confused about Sharepoint Spoke setup

jw9
Tera Contributor

Hi,

 

I am trying to setup the Sharepoint Spoke but there is conflicting information about how to

 

The docs detail several steps from creating JKS-certificate to adding JWT keys and JWT provider and then creating the OAuth Profile and connection.

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/administer/integrationhub-store-spokes/task/configure-ms-sharepoint.html#configure-ms-sharepoint

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0788079

 

This support KB article on the other hand only says to create the OAuth profile and the tenant with a different Token URL than in the docs.

 

I have tried both methods but failed to connect after following all the steps.

 

When following the KB article: Able to Get Oauth token via the Credentials form but getting 401 - Invalid Authorization Token when actually testing the spoke.

 

When following the docs: Not able to get OAuth token via the credentials form - 

OAuth flow failed. Verify the configurations and try again. Error detail:invalid_client, AADSTS700027: Client assertion contains an invalid signature. [Reason - The key was not found., Thumbprint of key used by client: 'xxxxxxxx', Please visit the Azure Portal, Graph Explorer or directly use MS Graph to see configured keys for app Id 'xxxx'. Review the documentation at https://docs.microsoft.com/en-us/graph/deployments to determine the corresponding service endpoint and https://docs.microsoft.com/en-us/graph/api/application-get?view=graph-rest-1.0&tabs=http to build a query request URL, such as 'https://graph.microsoft.com/beta/applications/xxxx']. Trace ID: xxxx Correlation ID: xxxx Timestamp: 2022-03-23 09:00:24Z, https://login.microsoftonline.com/error?code=700027

 

 

1 ACCEPTED SOLUTION

My issue was on the Azure application side. One of the permissions in the Azure App was setup wrong. We did not have delegate and application permissions setup correctly. I think we had the application permission setup as a delegate permission.

  1. Under API Permissions, add the Microsoft Graph permission:
    1. Click Add a permission.
    2. Select Microsoft Graph.
    3. Select Delegated Permissions.
    4. From the Sites list, select Sites.ReadWrite.All permission.
    5. From the User list, select User.Read permission.
    6. Click Add permissions.
  2. Under API Permissions, add the SharePoint permission:
    1. Click Add a permission.
    2. Select SharePoint.
    3. Select Application Permissions.
    4. From the Sites list, select the Sites.FullControl.All permission.
    5. Click Add permissions.

 

View solution in original post

15 REPLIES 15

Hello. Could you give me some more details on this? I am facing same issue

Did you solve it? I have the same issue.

Sebastien Pich_
Tera Contributor

have Similar issue did you Foud find_real_file.png

My issue was on the Azure application side. One of the permissions in the Azure App was setup wrong. We did not have delegate and application permissions setup correctly. I think we had the application permission setup as a delegate permission.

  1. Under API Permissions, add the Microsoft Graph permission:
    1. Click Add a permission.
    2. Select Microsoft Graph.
    3. Select Delegated Permissions.
    4. From the Sites list, select Sites.ReadWrite.All permission.
    5. From the User list, select User.Read permission.
    6. Click Add permissions.
  2. Under API Permissions, add the SharePoint permission:
    1. Click Add a permission.
    2. Select SharePoint.
    3. Select Application Permissions.
    4. From the Sites list, select the Sites.FullControl.All permission.
    5. Click Add permissions.

 

Hi Dan,

Although i am getting the same error you did, i wonder if you could let me know which details you put in flow designer. I am not sure what to put in the LOGIN NAME field in the "look up user information" activity.

regards,

max