Comments on: Use Azure REST API without interactive Login UI (Service Principal in Azure)/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/Professional Development, Data ScienceWed, 03 Jan 2024 15:52:46 +0000hourly1http://wordpress.com/By: Shahyad Sharghi/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-42529Wed, 03 Jan 2024 15:52:46 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-42529It was very helpful. It seems a little old.
I needed to add /v2.0/ to the url

POST https://login.microsoftonline.com/yourtenant.onmicrosoft.com/oauth2/v2.0/token

see the powershell script here:

Use Azure REST API without interactive Login UI (Service Principal in Azure)

Like

]]>By: freebet slot/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-30987Fri, 03 Apr 2020 22:07:41 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-30987Nice answer back in return of this question with solid arguments
and describing all on the topic of that.

Like

]]>By: Sheree Wurst/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-30956Wed, 01 Apr 2020 03:29:17 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-30956Can I simply just say what a relief tto uncover someone that geenuinely
knows whzt they’re taljing about on the net. You certainly realize how to
bring a problem to light and make it important.
A lot more people really need tto read this and understand thi side of the story.
I wass surprised you aren’t more popular
given that you certainly have the gift.

Like

]]>By: Ryan Wood/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-30826Thu, 26 Mar 2020 01:12:26 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-30826In reply to Tsuyoshi Matsuzaki.

Thanks so much for the update. I discovered that the problem was with my account not having the requisite permissions.

Like

]]>By: Tsuyoshi Matsuzaki/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-30825Thu, 26 Mar 2020 00:37:01 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-30825In reply to Tsuyoshi Matsuzaki.

Now I’ve changed resource id (changed to meet the current spec) in my post.

Like

]]>By: Tsuyoshi Matsuzaki/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-30132Wed, 05 Feb 2020 06:25:25 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-30132In reply to Ryan Wood.

Sorry, but this is old post and this resource id (https://management.core.windows.net/) is for Azure classic management.
Please use “https://management.azure.com/” for current Azure resource management.

Like

]]>By: Ryan Wood/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-30119Wed, 05 Feb 2020 02:01:37 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-30119I think this article is out of date. I attempted the same procedure but I cannot use https://management.core.windows.net/ for the resource on the authorization request because if I do I get an error stating that the “resource principal named https%3A%2F%2Fmanagement.core.windows.net%2F was not found in the tenant”. However, if I use the app ID URI then it’ll work but the resource request will fail with “The access token has been obtained for wrong audience or resource”

Like

]]>By: Tsuyoshi Matsuzaki/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-442Mon, 08 May 2017 10:38:36 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-442In reply to Rohit Iyer.

It says that your provided JWT is invalid. Can you please check your JWT with JWT decoder (like https://www.jsonwebtoken.io/ ), and can you check that x5t (X.509 thumbprint) surely exists in header ?

Like

]]>By: Rohit Iyer/2017/03/03/azure-rest-api-with-certificate-and-service-principal-by-silent-backend-daemon-service/comment-page-1/#comment-441Mon, 01 May 2017 16:33:13 +0000http://blogs.msdn.microsoft.com/tsmatsuz/?p=5695#comment-441I receive this error when I’m following all your steps : AADSTS50027: Invalid JWT token. AADSTS50027: Invalid JWT token. No certificate thumbprint specified in token header

Can you please help me with this.

Like

]]>