As promised, I am back to my second post on this topic. In my previous post, I showed you on how to generate Authorization token of D365 online from Native Console App using the Client_ID.
We did that using simple HttpWebRequest and Response and did not use the ADAL (Active directory authentication library) as well.
Well, let’s dive deep here. Nothing big in my previous topic as the same thing can be done using ADAL and in a clean way as well. Then why use that construct?
We are talking of headless authentication here which means authentication without user intervention. Using ADAL, it was fine to generate the token from a Native console APP using the Client ID. However situations become complex when we try to do the same from an external Web Application which required the Client_Secret as well for generating the token.
So I created a ASP.NET…
View original post 300 more words
Hi.. a small query.. can the external API support mutual authentication?
I mean calling the service endpoint via client certificate?
LikeLike