![]() ![]() Let’s go thru some small exampels, simple GET example get comment 1, write the Method URL and HTTP protocol to use, so for a GET to using standard HTTP/1.1 it will be written as: ![]() Structure and semantics in this file is very easy, tactic is just write the request in raw format and the press send. http ending tells the Rest Client extension to VS Code it’s a http request and therefore adds a button on the top Send Request that will trigger the request. I’ve create a folder called D365 and added a file GetQuotes.http. As a standard I create a folder and add the requests there, it’s easier to reuse and modify for new requests. So first install the extension in VS code.Īfter this, let’s create a new Workspace and start testing this out. ![]() I found that VS Code has a nice extension that I will use in this case the Rest Client. So I started to look around and I found a good option for this, and that is what I’m going to share today. If we could use our own account instead of a service principal we would increae security, starting time and flexibility all at once. And second can’t we as a developer just use our own credentials and access? First is it a good idea to give all developers client credentials to access services? It takes time to create and these credentials is possible to share amongst others, even outside organisations. One thing lead to another and an interesting discussion arised with one of you, from that dicussion I had two questions ringing in my head. Soon after released I started to get questions, THANKS ALOT to all of you who reads and comments. Two weeks ago I did a post around how I use Postman to generate AAD Oauth tokens for Service Principals. AAD Personal Token in requests with VS Code ![]()
0 Comments
Leave a Reply. |