You might think, "If this access token is so easy to decrypt, why can't I just create an access token without authenticating to Azure AD and just send it over?" And this is where ADAL comes in because this access token is actually signed, and Azure AD will verify the authenticity of this access token. It even tells you what permissions does this access token have. We just paste the access token here, and you'll see that this is actually a valid access token. One of the tools that I like to use is jwt.io. This access token, you can actually decrypt it using a number of tools. ADAL JS automatically put this access token on top for me, and it is also going to renew this access token for me. That's great, but you also notice if I click on this me request that we sent, and look at the request headers.
When I click on Run Command, you see that the results show up. I'm going to clear out the Network tab and click on Run Command. All of this has been done by ADAL for me. But I'm going to click Login and a whole bunch of authentication (mumbles) just occurred, and you see that a number of things got populated here. Let's go to the Application tab and see that under Session Storage, there is nothing there right now. This is the port we had specified that our website should run under, and also, this is specified as an acceptable redirect URL for my app registration. This'll fire up lite-server as we expect, and it opens the browser and takes me to localhost:4200. Let's go to Command Prompt and say npm start.
It is time to run our application and see the fruits of our labor.
0 kommentar(er)
