Sharepoint spoke setup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2022 10:27 PM
Facing issues in setting up the Microsoft sharepoint spoke. I have configured everything as specified in the docs but the Get Token action throws the below error:
Verify the configurations and try again. Error detail:invalid_client, AADSTS700027: The certificate with identifier used to sign the client assertion is not registered on application. [Reason - The key was not found., Thumbprint of key used by client:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2023 01:15 PM
were you able to fix the issue ?
Are you using Oauth 20 as the authentication type ?
Any specific reason certificate or thumbprint is required ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2024 12:14 PM
Hi,
Did you happen to solve this problem because I'm facing the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2024 03:08 AM
hi muhamali,
Could you please confirm the following:
Which Version of SharePoint Online Spoke is being used?
The correct Certificate (.cer) file has been uploaded on the Azure Portal App and is valid and .jks/.pfx was created as part of the same certificate generation process.
The thumbprint value is copied fully ( you can use manifest as well) and converted to Base64 before adding it under the connection attribute via the connection (not directly on the alias attribute).
Although you have not posted the thumbprint value here on the question due to security concerns, you can verify if it is the same is available on Azure Portal.
Please share your findings.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2025 07:33 PM
Hi @muhamali @Sravan Kumar Ka ,
Were you able to fix the issue? We have followed the steps in Configure Microsoft SharePoint Online connection record and we are also getting the same error. We have already update the jks, was validated successfully and converted the hex thumbprint value to base64.