Making the chicken dance one line of code at a time
Lets make the legacy app work with the new stuff
Legacy software is fun. Sometimes we need to update code to enable new authentictaion methods. In todays adventure our intrepid developer heads off on the quest to get the legacy .net framework 4.6.1 WinForms app working with the new user store, AWS Cognito.
So many options to do things badly, so few to do it right
Once again we enter the scene with the developer manager trying to figure out what the best way to secure the applications are. This one is different from the API gateway since it is meant for users and not just automated access. The additional wrinkle is that as part of this project we wanted to add SSO to our reporting portal, a soon to be built order entry portal, and a client invoicing portal. So three different apps, one being migrated from Web Forms, one a third party product, and…
Reflection, Microsoft.Extensions.Configuration, Microsoft.Extensions.DependencyInjection, and a healthy dose of not stopping to ask if we should.
When working in multi-tenant systems being able to swap implementations based on which client is logged in can be very helpful.
Its been written before but maybe this makes more sense to someone
At work we are currently going through a migration to modernize from a .net 4 winforms app to a modern web app with HTML, CSS, Javascript, and .net core on the backend. Part of this is also making our permissions more manageable and centrally applied so the same logic is not in 6 different places.
Why can't things be simple
Recently I have been working on an API and wound up running into an issue where a third party application would happily take “Invalid” XML and continue on the way. The main culprits were out of spec acceptance of boolean and date fields.