Microsoft 365 Community Identity platform, 20 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Migrating an ASP.NET core application to MSAL from ADAL – A developer journey – December 2022

Description

This month’s in-depth topic: Migrating an ASP.NET core application to MSAL from ADAL – A developer journey.

Azure Active Directory Authentication (ADAL) family of libraries are being depreciated (https://aka.ms/ADALPost). We have an advanced, modern, and more secure library - Microsoft Authentication Library (MSAL). Join this call to learn the migration journey, we will be migrating an ASP.NET core application, which is currently utilizing ADAL to MSAL, demonstrating a detailed code walk through and steps to be followed in the migration journey.

Microsoft Presenters: Kyle Marsh, Pramod HK, Jitesh Nair, and Bogdan Achim.

This call was hosted by Nandeesh Swami (Microsoft), on December 15, 2022.

Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365/blog
• Mark your calendar for next call on January 19th at 9:00am PT. Download the recurrent invite for this call | https://aka.ms/IDDevCommunityCalendar
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community

A

B

Public Community call where we have an interesting session every month. This month, too, we have an interesting session on MSL we're continuing our MSL series. We started with M cell integration and um you know how do you integrate Azure ad into your react? Applications angular applications and we did one on electron, desktop applications, and then we also had a video on. You know how you customize claims and all that. So if you have not checked out those videos or you could not join those calls, I will be sharing a link of a YouTube channel.

B

Where you can view all those recordings. There's a playlist that I've created. You can look at all those videos, so just like every month this month, too, an interesting call a line for you. We have a great amount of speakers today, our architect Kyle, who is uh who's. A very frequent uh speaker on this platform, is there in the call. Today we have uh three new faces: uh promote jitesh and Bogdan. um They all are from our uh identity, Ace team who work with our customers, helping them resolve their scenarios.

B

I'll, probably let them introduce themselves to you, but then, this month we're gonna concentrate on migrating, an asp.net core application, which is uh you know using it out to msel all right. We already know the drill we're regarding this call. If you don't want to be part of the call that is getting recorded, feel free to drop.

B

We're going to share a survey would love to get your feedback on the the session and also what kind of topics you would like to hear from us so feel you know, I'll be sharing this link in the survey. Please go ahead and fill that out. We have this YouTube channel, which I'm gonna get share on the uh the chat uh which has a list of all the videos that we've been doing for a year or two.

B

If you missed out any of the videos, go ahead and check it out, you can follow me on LinkedIn to know what's coming up next on the platform Community call or in general any of these activities that we do on Azure ID developer right. You can also follow us on Twitter at Microsoft, 365, Dev or Azure ID, where we not only put things about these events and programs, but we also talk a lot about product.

B

The next call is going to be in January, it's going to be January 19th, and uh it's going to be on graph uh again. An interesting call lined up for all of you folks, based on the suggestions that you provided the survey so before uh you know I hand it over to pramod. If you have any questions, feel free to put that in the chat. Again, we would love to get your. uh You know inputs on what you want next, so feel free to put in those comments in the survey.

B

So, with that I hand it over to promote pramod, if you want to quickly introduce the team and then uh get on with the call.

C

Okay, thanks uh nandish, hello, everyone. This is pramod here, as sanandeesh mentioned, I am part of our Ace app and Dev team, where we will be working closely with our developer customers, uh assisting them integrating uh uh integrating their applications in application to Azure ad.

C

So we have I think we have a Kyle Marsh in the call as well, who is in the architect who is from the architect team. Along with that uh we, you know, we have a couple of my colleagues as well who will be driving through this. uh This call that's a quick intro about us, so yeah.

A

C

Let's look at the agenda for today. Okay, so I think um why I know uh today, uh the main mainly we will touch upon these points. uh We will quickly start. You know we will briefly talk about. Why do we need to migrate an all application to MSL? uh You know quickly to understand what are the reasons we need to migrate and then then, we'll jump on to some kind of a Hands-On, a kind of experience.

C

In the sense, um uh let us say if you have a web-based application, will mainly focus on the area as a developer. What are the steps or what are the things that you need to do uh to migrate, your application from agile to msat? On that Journey uh we are taking an example here that is nothing but asp.net core web-based applications. uh There are a couple of options that we will evaluate today. uh One of the option is, uh which is the recommended approach, is uh moving an asp.net core application from adult to Microsoft.

C

Identity.Web I will explain what is Microsoft identity toward web in the demo, while I talk, while while I get to that part, and also there is another approach where we could use the adele.net in asp.net core web-based application and migrated to msi.net. So those are the two options we will walk through and then finally, we will have a quick summary on the things that we touched upon. So that is the agenda for today's today's call.

C

So just to summarize, uh you know, basically we will be mostly spending our time on how to do the migration I, don't know what are the steps that we need to take rather than you know. Why do we need to do the migrations, so yeah uh next is I. Think most of you might be aware on. Why do we need to migrate?

C

So you might not be aware of the fact that adult library is in a duplication uh as a notification path. No features have been added to adults since June 30th, 2020 20, and there are no adult features released, planned either. So, whatever the you know, Focus or the energy or the efforts from Microsoft standpoint, all those things are going through the M cell.

C

So that is the one of the reasons why you know it is important for an application which is using adult to be get migrated to MSL so that they can be up to date with the security related fixes as well. Along with the security related pixels M cell does offer additional features such as continuous access, evaluation, auth, broker, support uh certificate, Azure ID certificate based authentication on mobile, and you know system browsers on mobile devices as well.

C

If you are interested in under understanding what these capabilities are, I would suggest you to go through our landing page on adult to MSL, where we have clearly defined uh what what are these features? How do we enable them- and you know how M cell, uh using MSL, how you can leverage all these features? I will try to touch upon these features. uh While we do the migration, but mostly as I mentioned earlier, I'll focus on the coding part or the uh the steps that we need to take to migrate.

C

The application with that I think maybe I'll quickly share my screen, so we discussed we understand uh the the thing is we need to. It is important for an application to migrate to amcell now I I'm, taking an example uh here. uh This example is one of the more popular examples that were available. That is still available in our uh in official page, where uh it is a webasp.net core web application. Calling a web API, which is in asp.net core uh I, would presume there are a lot of customers.

C

You know who have referenced this adult sample and build their application on top of it right. So what I'm doing here is I am taking the same sample which was put up, which is using the Adele and and making that migration move over here. Just to give you a context, this is simple web-based application uh written in aspeak.net core 2.0, and it also has a web service. uh You know there are two uh API calls or um I would say: controller API controllers get 10 set, it's basically a to-do item.

C

You can just put a string. It will add that string it'll also list the string right. So these are, this is the API. This API is called by this uh web uh web app right so to call this API web app is basically doing the authentication, while it does the authentication, it is also acquiring the access token and stitching that access token in a better header and calling the to-do list service. So let me just quickly run this sample just for your reference, how how it basically looks like so uh when I ran this.

C

It is loading uh you know both API running the API application, as well as the web, app application. So, while I you know this web application is loaded, it is taking me into the authentication page. So if you can observe here itself, you know it is using the V1 end point: there is no B2 uh in the in the URL. That itself is an indication that the application is using. Add okay, so let me punch in one of the dummy okay.

C

So let me just use the dummy user over here, so I'll go ahead and I'll hit in the potential, so.

C

As I mentioned, this is a you know: basic web-based application, which is uh which has prompted me a to-do list. So when I click on the to-do list, it is making a API call to that AP better token. So if I say one two, three I can add a 2-do list item, and you know maybe I'll add one more four: five: six, that's it. So this is a typical web application, calling a API uh architecture.

C

So, as I mentioned earlier, there was an indication that it was using the v11 point, which indicates that it is an adult application from an admin perspective. How do you identify uh this application is using uh using you know adult Library? It's basically, you can rely on a sign in logs right. So uh they'll, be you know. I just you know, ran the sample, uh maybe 15 minutes ago and I could see that uh you know I just came here and I clicked on this and additional details.

C

Information I can clearly see that you know this application is making a call using adult a library right. So that is one of the factors. As an from a admin perspective, you can look at the I assigning sign in logs to see that this is an adult application. Another approach would be to. uh There is a you know. If you go to the adult to MSL migration, latting page as I mentioned, there is also a link uh where uh we could monitor the workbook solution, which will list the adult apps as well.

C

So, for example, I have already configured that workbook in my tenant. If I go to the workbook Solutions and click on the sign in the information in the last four hours, I sh, you know my, you know there is a separate section which will have a specific queries. You know store queries which will list the adult application. So here we see there is a. There is a sample application that is Community Live to-do list and it is using the adele.net library reference. So this is from the admin perspective as a developer.

C

How do you identify that your application is? Is using add-on? It's just you know. Maybe you can have a search on um a namespace called Microsoft identity model clients.active directory. If you find that uh in your in your project, that means it is using the adult another popular or one of the main class in Ada library is called as authentication context. If you search the authentication context class in the project, and if you see that uh you know if it is available, then yes, that means this application using the add-on.

C

Just to give you a perspective on on how this this uh web application is running is, if you look at the startup, it is basically using the open, ID module of the asp.net core to authenticate the user. Along with the authentication, it is using basically the hybrid flow to get the authorization code and from the authorization code. It is it. You know, I think we are subscribing yeah. So if you see here in the code or in on authorization code received, uh we are creating a class called authentication context which exist in the Adele Library.

C

We are creating an object, object and acquiring a token via authorization code flow right. So and then, while we make the to-do controller, you know in the to-do controller view before we call the API, we try to acquire the token silently here. Is the code acquire tokens Island, uh you know, whatever the access token that we have acquired from the authorization code flow. We will get that token over here and Stitch it to a bearer token and then finally make the API call right.

C

So uh from a developer perspective, I know this application is using adult. Now, how do I go about it right? So I want to migrate this to the latest library that Microsoft offers right. So uh if you again, if, uh if I'll be referencing uh you to our landing page on, add to MSL where we have a guide, uh basically on adult.net and mcl.net for each platform, for that matter, we have a separate guide which will explain the step-by-step procedure to make the changes on your application.

C

So in this application, what we have seen is you know adult mcl.net. So there are two options: I have two options. One of the options is there is a library called Microsoft identity.web, which is nothing but a wrapper built on top of mcl.net and has additional capabilities or additional features specifically for web-based application and web apis right. So that is exactly this. Flowchart describes you, for example, uh if you want to, if you want to choose between Microsoft, identity.web and mcl.net. Here is the flowchart that makes it easier for you to choose.

C

For example, the question is whether your dotnet application is a web-based application or not. If it is not, if it is a desktop console app, uh you know you should go for mcl.net if it is a web-based application, whether this application is using asp.net core. If it is asp.net core, then you go with the Microsoft identity.web. If you are building a new application, we recommend you to use the project template.net core project template. If not, you need to make the manual existing changes right now.

C

In our case, we know that this this this you know my I already have an asp.net core application, which is using at all now I have to migrate it to identity.web right so I have to do the some manual changes right. So that is the approach that I will be taking uh over here.

A

C

Another approach is, you know, we could also use the mcl.net in asp.net core web application, which is something that is my colleague bogged and will walk you through once I'm finished, with the migration from adult identity.web. Okay. So now let me do that. So let me close this uh application.

C

um As I mentioned earlier, this application is in asp.net core 2.2, which is a unsupported version of the Microsoft, and also our Microsoft. Identity.Web is not compatible with with asp.net core 2.0 and hence what I have done is I have migrated this asp.net core 2.22.net6, which is the minimum supported version from Microsoft standpoint. How do we migrate I just followed the instructions that we have on.net core 2.22.net, Chex migration or step-by-step procedures? Of course, there are some manual changes that I had to do so.

C

I have already made made those changes in this sample, so then I also kept that sample in the GitHub repo, as well just for reference. So what I'll do is here is instead of taking the asp.net core 2.2 project. I am I will take the project which is migrated to dotnet6, as I I'll not be going through. All the steps of the dot net core migration, because that is something that is out of scope of this. uh This call so I'll take the migrated.net 6 project as a base.

C

Point and I'll try to remove the reference of a dial and try to use uh the identity.web okay, so I all I have already ran this or cloned this project, and my application is, if you can see here, it's already upgraded to.net6 right. So, let's see what are the changes it? It takes to use the identity.web okay, so I have a documented some of the changes that we need to. uh We need to do um because it's you know. We need to just try that out. For example, First Step would be to identify adult reference.

C

I already showed you how? What are the keyword? Searches that you need to do to search the adult references right, authentication, context class as well? As you know, the name space that you can search I can clearly see that these nuget packages are available. Let me get up get rid of this nokit packages by the way web API doesn't need, doesn't use at all, so I don't need any changes in the web API. So whatever the changes that I am doing, it is in the web.

C

App okay, I'm I have got rid of the references of pedal. I have to install the nokit packages. Microsoft identity.ui, as I mentioned uh identity.web, is a wrapper on top of mcl.net.

C

Similarly, uh there is another package called identity.web.ui, which is another wrapper on top of identity.web, which will also which, which gives additional features of authentication, meaning the UI sign in and sign out or, although now, basically, when we have sign in and sign out right, so those two options are also handled by this identity: dot, web dot, UI in addition to this identity.web dot, UI I'm, also using a reference of Newton soft. Let me quickly install that nokit package as well.

C

Okay, so now I think, uh let's let's, let's, uh as uh you know, let's comment out some of the code, which is not necessary in case of adult. So um in case of identity.web sorry, uh here, as I mentioned, uh it was using the authorization code flow right. So uh after the first leg of the authentication the code is received and then the code is exchanged with the access token. So we had to have a manual code explicit code, to do this stuff right.

C

So we created adele.net uh adult object, which is nothing but authentication context and then then got to access token. So all these things are abstracted in identity.web. Identity.Web will take care of all this. uh You know subscribing the event and getting the token all those things are handled. So we can, uh you know straight away, comment uh or maybe what I'll do is I'll delete this whole file itself.

C

One more option is uh reading the client ID tenant ID secret. All those information are again taken care by identity.web by by itself, so I don't need to have a separate class for that as well. So I have deleted that reference too. So now identity.web also provides me in memory cache as well. So I don't need this code, where I have written a native session cache to update uh the cached information into into the session and then read it. So all those things are taken care by identity.web itself. So I can remove this file too.

C

Since I am using the account, uh you know, identity.web dot, UI Library, my sign in and sign out controller actions are also handled by that Library itself, so I can remove the account Controller Plus as well right, so I'm good here. So now what I'll do is in the startup.cs class. So, as I mentioned earlier, this is used dual of asp.net to core. uh You know uh to to do the authentication, so let me get rid of this.

C

uh This part and and use our laptop. You know paste some of the namespaces that I'm doing it over here, so that I can reference the identity dot web. So uh I will go ahead and paste this over here. The important thing to be noticed is I'm I'm hooking, this middleware called uh add Microsoft identification, web authentication and passing the configuration object. Okay, along with the configuration object, I'm also saying that I would like to acquire the token to call my API right.

C

What are what are the API that I need to call so uh go and look in the configuration? That's nothing, but in the to-do list, scope right. So this is the configuration that I need to update it, which I will do it in a while and also for the demonstration purpose. I am using the ad in memory token cache not just to replace that session, cache that at all I used to use and then in order to use the sign in and sign out controller action.

C

I am also using the add Microsoft identity, UI middleware as well. Okay, so that that is done. I'm good, so I have to use the Json right, as I mentioned I'm, saying explicitly saying to the library that I need to acquire the token while I do the authentication, so it will what it will do is it will look for the section called To, Do List scope uh in my app settings.json, which is not available in adults. So what I'll go ahead and I'll just paste?

C

This one so API IP, ID and user impersonation, so I'll have to update this as well. Okay, uh I think I had uh basically I have to use this uh domain and the Tenant ID information, which I will do it right away. One second I have to I, did not I had not updated the latest stuff over here. So what I have to do is I have to basically update this over here. Just give me a second, so basically, what I'm doing is this application? Whatever the migrated?

C

Application is I, just cloned it, but I haven't basically replaced this setting. So let me what I'll do is probably after this changes. Let me just run the other one so that it will be easier to track it out. Okay, so now that change is done, so I can do the other changes later. So this is good and then I have to move to the to do. uh Controller. Give me a second over here in the to-do controller. So, as you can see, it is complaining about the ideal references as I have removed the adult.

C

I know the package that was installed so I can comment. This of this comment, this code and I also need to use the identity.web references right. So what I can do is I? Can I'll just declare these variables and create a Constructor I'll explain what what this can instructor is all about is, as you as you can see here in in Adele. I was acquiring this token, silently from the session cache right.

C

So, instead of that, what I have been doing over here is I'm using one of the class called token acquisition clause, which is present in the identity.web, which is again one of the wrapper to the class that mcl.net offers as well.

C

So this what it does is it's basically it tries to you know it can get you the token, silently, whichever is available in the cache right, so that is what I have been using I'm just making use of the dependency injection feature so that these objects are built enough right so and I'm also creating one method called prepare authentication where I'm using the token Acquisitions class to get the token get access token for user as think right and then stitching to a better better token.

C

Now uh what I have to do is I have to delete this code. Right authentication result is not required and also I need to delete all this code, because this code is basically I'm trying to acquire the two consistently using adal. Instead of this, what I can do is I can just simply use the code that is referenced in the uh you know. Using identity.web I can call the prepare authentication client I made this object as a global object. Http, client and then HTTP client directly calls the API for that API.

C

The bearer token is already stitched, so I'm good here in the process. Unauthorized method, I think we are using the adult reference, so I can get rid of that adult reference as well and I. Can you know, redefine this method process uh unauthorized without adult preference? Okay, so we I, don't I mean if you look at this code. Oh no I just commented this code right. uh The commented code is, you know.

C

Basically, we are explicitly removing the cache Etc and you know doing some kind of a manual stuff with adult, but identity since identity.web takes care of all these things. Like no I can just comment of that course as well, so this is the get index method. That means, when I click on that to do list. That's when this action gets controlled right. So that means it is calling that get API now I have to repeat the same to the post API as well.

C

So let me do that so I can get rid of this authentication result. uh Reference and I can also delete all these things where I'm trying to acquire the two consultantly.

C

Instead of that code, I can use the simpler code over here, which will acquire the token for me and just just serializing that token I mean sorry the object and then passing the poster sync method, one more I don't need authentication context class as well with that I'm I'm, pretty much done with my you know, removing the adult reference and making use of the identity.web reference I think the last few changes are related. uh Okay, so I have to use the identity.web dot. Ui sign in and sign out features right.

C

So what I have to do is I have to go to the basically views under the shared folder. There is a login partial, so here we are using the account controller right. So, instead of the account controller, let me use it from the Microsoft identity, a controller as well. Okay, with that, my changes are done. Only the change that I need to do is basically update. This client ID related information that I'll do it right away from the working scenario I'll give yes.

C

As web web API 2.

C

Okay, so let me just compile this: hopefully it builds.

C

Okay, it's succeeded, so let me quickly run this sample, so you can observe uh you know we can. Just do uh you know just compare the user experience, so we just followed straightforward. You know uh steps right. So it's just a uh you know. Instead of the adult code, we just use the identity.web straightforward. uh You know with the with following the instructions and as you can see here is the indication uh you know. Application is already migrated to MSL because it is using the V2 end point right.

C

So let me go ahead and punch in the credential of a test user.

C

It was asking the sign in because I'm using the incognito window, so there's no SSO, so it just prompted for the username and the password and I'm done so I can click on the to-do list so which will call that API as well. So maybe.

A

C

Will add it so both get and post methods are done right. So if you see here, there was no absolutely no change from the user experience right, though I have changed the complete authentication model from adult to identity.web from the user aspect. There was no absolutely no change from the user experience right. So that was an indication. One of the indication was, as I said in the address bar, it is, you know, basically will be using the V2 V2 endpoints.

C

So now, if you, if you are interested uh from, if you want to verify that MSL is, you know, actually is getting used, so you can also go to the sign in logs from that main perspective, and you will see that instead of the adult.net library, you will see the mcl.net library over here so that completes our migration Journey from adult to MCL or.

B

Identity. with that, can we hand over to Bogdan um there's just a couple of questions, so you used Newton soft libraries that a requirement no for the migration. No, so you can use any other library that you know you.

C

Know that yes,.

D

Yeah perfect yeah.

C

I just changed a few of the codes where I had to do the you know to do list. There was an object called to-do list which I had to say: let's see, realize I can do without the Newtons of Json as well.

C

That's good before I hand it over to Bogdan I just wanted to give a quick walkthrough of uh you know, though. We have migrated your application, so uh you know now. Your application is, of course, is more secure in a way that the new features Advanced feature will go through the amsa library. So if you want to use, for example, uh one of the features like right instead of the secrets, if you want to use the certificate, there's simply few configuration changes that it it requires.

C

For example, if I just update this and update my certificate in the key Vault, and you know upload the ACs CR file uh to our app registration uh identity.web will take care of all these things connecting to keyword, and you know getting that public key private key and all those things and trying to match. So we don't have to worry anything. So it is just a few lines of configuration changes and you are good to go uh if you want to use a distributed cache in web application. That is also pretty much easier.

C

We we provide built-in support for reddish cache and the SQL. You know Service as well. uh You know, uh you know we'll share the link where you know you can just use this distributed cache in place of uh in memory cache as well. That is again just a middleware. uh You know a component change, that's it I think there's not much code as well. You could also use the identity.web in the API project as well, uh which will take care of your token validation in the present sample that had simply demonstrated it.

C

It was using the Azure ad.ui, Library I know you could also use identity.web which can take care of this scope, validation and the token validation stuff as well. So if you want, if you are interested or if you want to do that in the API project, so there are steps that we have documented in one of the reports which you can just follow it um as the sample.

C

It had only one scope, uh you know in this sample where we just acquired the user, impersonation scope, and then we just simply called the API because and I'll. You know basically in NL World, we we request the token for a resource rather than specific permission. uh You know in m style world you could specifically more granular level of scoping.

C

You can uh request, for example, if you, you can acquire a token for read permission and at the same time you can do for the right permission and we can segregate between these Scopes, and you know you know, build your logic. On top of that, uh you know. If again, it had two controller actions right. So if you wanted to have a separate granular permissions, you could do with the to-do list read and to read right. So what are the changes it takes?

C

That is also a very minimal changes that it requires on the on the projects. Again, uh if you have a large software, where there are multiple modules built on top of it, when you sign in you know, it is especially true when you have a new application right building a new application. So you may want to have, like you know, instead of showing a consent prompt for the users where there are a lot of consent uh screens, you could incrementally request for the consent.

C

That kind of a feature is also available in the nsap proof of position, tokens that is again built on top of the MSL library. That means uh instead of access or Bearer token techniques. You could also use the pop tokens, which is basically bind to the user com device so that it becomes more secure. So, if you are model in, you know want to explore that option. Yes, no, it is available in our talks as well.

C

uh One more is continuous access evaluation. That is, uh you know, basically allows to access token uh to be revoked. You know when some critical events happens and then so that you can have a more secured application, so this uh continuous CAE feature is available in our graph API. At this moment. uh It's you know. If you are, if you want to build your web API in CAE, that is, uh you know, it is not available yet in public, but if you are using the graph API graph paper, it does completely support.

C

Let's see feature as well yeah. These are the you know some good to have a nice to do things you know to in your application after you migrate, your application from Halal to answer. So basically it will enable all these features. You know for you to implement as a developer in your application.

C

Yeah, that's all from my end I'll hand it over to my colleague Bogdan, who is going to walk you through the same sample instead of using migrating to identity.web. He will migrate it to mcl.net over to you about. Thank you.

D

Okay cool. Thank you very much pramod, so we have scenarios where developers cannot use Microsoft identity web and they can actually go with integrating directly msl.net and Microsoft identity web as a hybrid model. We have the the second sample from our repository. We are starting from the same startup application and we are actually documenting in the in the second article, the steps that need to to be taken.

D

So we have the same scenario: web application that needs to consume a custom API and due to the fact that we're only targeting to migrate the application from adol to MSL. The only place where we have adol is within the the web application. So that's the only place where we're gonna do the um the migrations. Okay. So, first of all we need to deploy some nougat packages.

D

Let me quickly switch to the nuget packages. Let me search for them. Microsoft, identity, client is the library that contains msl.net. Let me just quickly deploy it. We should have some some end user license accept.

D

Now we got this one and also we're gonna have to use the identity web token cache. This is the mix that we're gonna use in here, because identity web will ensure that uh the token cache.

A

D

Okay, cool again accept cool now in order to to ease the the development. We're gonna need to add we're gonna need it's a best practice to add MSA, app builder class that we're gonna use along the way. So let me just go with adding a new item and we're gonna briefly go through what it contains.

D

Okay and now let me get the value.

D

Okay, oh, so what do we do here? We instantiate the confidential client, because we are talking about the web application, which can be a confidential client, of course, which is a confidential client, uh we're defining the the cache that we're using. uh We also have some comments around here on how to define the distributed cache and also the option of removing the an account from from the cache specifically calling this okay.

D

Then we also need to update the pager ID entification, build extension, and in here we're going to comment on uh the on code on authorization code received we're gonna comment, uh the pieces, we're gonna, delete them actually related to radon, so we're just gonna, delete them and we're gonna add pieces related to MSL, and in here you can see that we're acquiring a token based on the authorization code for the resource and the slash default scope.

D

Slash default will ensure us that we're going to have backwards compatibility with um with the ado application, so we're just gonna request for all the consented permissions that we have at this moment.

D

Okay, then we're gonna go to the actual place where all the the idle calls are happening here, and this is the to-do list controller.

D

So before adding the.

D

The places where we're using.

D

I, don't know exactly why this is not commenting, it should comment yeah. Well, we had to do another shot. So at the moment when we commented um adol the idle reference, we can see all the places where we have actually calls done to to Adolf, and these are the the points where we're gonna need to to take action overall.

D

But let me just go with the references that we have here to add: we're gonna, add identity, client, identity, web and sp.net core http, okay, and we can remove or comment the the up the call to uh and to Adolf, and this will highlight all the places where we have to to do changes. Okay, we're gonna, add, of course, a Constructor to the to-do list.

D

Oops sorry, wrong line: okay, uh we're also gonna, add and get authentication result and get authentication result is the one that's going to help us with uh with the token, because here we're gonna, do the token acquisition, the silent token acquisition, okay and we're gonna reference this one along the along the way? Okay and now in the index controller, we're gonna, remove the Fatal references and we're gonna add the much simpler way of integrating with MSL.

D

So we're just gonna do a call to get the results here for this, for this resource, of course, that we have this one, also on the post controller, so I'm gonna do the same. uh The same step here: okay, now due to the fact that we also have the reference to uh process unauthorized, and this one was containing the auth context, we're just gonna remove the the calls from here the references to to the auth context, because we no longer need them and we're also going to go to the actual process.

D

Unauthorized, remove the and remove the code.

D

That belongs to Adon, okay, and this was the migration that we did just adding rsl.net to the solution. And now let me just quickly go run the solution.

D

Okay, in the back end, we can see that the API is being loaded. It's loaded at this moment, and now we're gonna have to call done for uh for the Authentication. So let me quickly log in so. The authentication at this moment is still happening with the um asp.net core 2.2 components from the from the application and we're requesting for uh for an X for an authorization code that authorization code is used for getting the access token for the to-do list API, and that that's the point where we're using MSL at this moment.

D

So this was it um from just adding adol, uh just adding MSL to your solution. I think we can also go briefly to to the summary uh what I wanted to to add to this summary. During this call, we have briefly identified the reasoning for migrating from adult to MSL and the techniques for identifying where adol is actually used and we've seen two approaches for migrating: an application from adult to MSL.

D

We have the approach when using the the identity web, which is the recommended one and which Pro Mod has demonstrated, or just the the scenario where, for example, I was having an asp.net core 2.2 that cannot fully integrate with identity. Web and I actually did the In-Place replacement of adol with msl.net. Only on those specific calls, because we have to ensure the security of our application, and maybe we want to leverage different security features which MSL is actually capable of doing an adult is unable.

D

So we can also see that once you have identified the pattern once you go through through the documentation, the the actual investment is in doing this. One is not much because when we had the we had identified the pattern both me and promote did do app migrations in less than uh I. Think 45 minutes at this moment who are fairly fairly simple, simple migration. So it's not very hard because, even though you may have a very complex application with a lot of endpoints, the authentication bit is pretty much the same on all the endpoints.

D

So you shouldn't encounter too much of a struggle once you have identified the pattern and once you have identified where you need to do the code changes in your solution and of course you can create the internal repositories and everybody can leverage those.

B

I mean it's, it really put into perspective as to like how easy it is to move your Ada lab stream cell apps, and essentially, why is it really important to move to MSL right I mean uh that is that's really something that we sort of got the messaging through uh this session. uh Thanks a lot for that. So uh before we close any closing comments for our developers on the call.

A

We're very interested in any of your journeys of migrations from Adela emsel we're happy to help, uh and we appreciate your time as we go through this. So thanks everybody for your time today and enjoy the rest of your day.

B

There you go guys looking forward to all your migrations and all the questions that you have for us thanks a lot for joining next month. Again we're gonna connect. We have again interesting calls I have put in the survey link. uh It would be great if you could go ahead and take a quick survey for us. The next call is on January 19th. We're gonna have a call on graph, an interesting call, an interesting speaker. Again, uh we will be putting out our amplification messages on LinkedIn.

B

You can follow me on LinkedIn, as well as our Twitter accounts, Microsoft, 365, Dev or Azure ad thanks a lot for your time. All folks have a good one. Bye.