In my previous article, I explained that every company has to think about what they want to do with the old AngularJs application? For some companies, it’s better to completely rewrite the application. Maybe even not in Angular anymore? (if you have the resources for it) And for some companies, it’s better to create a hybrid situation/application in which you can let the AngularJs application, with new Angular components, co-exist. This can really help you to easily make the transition from AngularJs to Angular.
This blog post is the first part of a series of blogs that will help you to take a look at a hybrid AngularJs/Angular application. Let’s start by setting up an environment for our migration.
AngularJs became very popular because of a set of features that really helped programmers constructing stable, scalable and robust web-applications. AngularJs reached the top segment of the market and was compared to ReactJs and EmberJs also a good choice to build your product with.
But all good things, come to an end.
These past few weeks I have worked on the implementation of OpenID within a Hybrid AngularJs / Angular application. For this implementation, I used the Angular OpenID client from Manfred Steyer. This client is OpenID certified and makes it easy to connect your Identity Provider (IdP). It supports implicit flow and PKCE code flow. There is also good documentation and examples so I am not gonna show you the code because it’s pretty clear in the documentation.
But what I do want to tell, is that by using implicit flow you are vulnerable to a couple of security issues.