In this era of artificial intelligence and the internet of things, it is quite common that everybody is focusing on automation and diminishing human intervention in various processes. Though IVR is one very common solution for the decreasing manpower in supporting system or helpline from the decade, it is quite difficult and lengthy process to integrate it with web solution to do automated processing based on user voice or key input on the call. Twilio comes up with the Twilio Studio which is a very effective solution with drag and drop option to create various flows and initiate HTTP requests to trigger actions based on user input.

As we all know IdentityServer is built with the concept of the central identity provider and it is supporting single sign-on by default as part of its main feature, but the single sign out is not coming as a part of inbuilt feature till IdentityServer3. Now they have added support for front-channel and back-channel specification for server-side clients in IdentityServer4. Here, I am going to explain how single sign out works using back-channel configurations.

Most of the applications in our internet world are having some automatic task scheduling mechanism like email reminders, expiry notifications etc. For small-scale applications, we can do this type of functionality by running background tasks. Quartz.net is one of the famous libraries to schedule background tasks in .net web applications.