Cookie based authentication against API isn’t common scenario but you would find it here and there, mostly in legacy applications.
HttpClient supports cookies out of the box, but it doesn’t work always as expected. In my scenario the cookie is always invalided by API after each call which results always to the following behavior: the first request is successful, every other is rejected. Let see how can be avoid it.
Cloud based applications are distributed in nature. As the times go it becomes more and more difficult to maintain an overview over all settings used across all of the components. Finally there is a new Azure service to store and manage application and deployment settings and feature flags in one place.
You don’t want that someone is calling your Azure Functions unauthenticated. You can rely on old-school function keys or use Azure Active Directory. Azure Functions provide elegant Authentication / Authorization functionality previous known as Easy Auth which works nicely with Azure API Management.
Indexing is important and can save significant costs and improve dramatically performance.
Well you can easy provide Azure App Service App setting in ARM template. Right? But what if you would like to merge settings included in script with those provided outside. This is another story.
OAuth specification 2.0 is out there since 2012 but 1.0a version is still widely used. Atlassian’s Jira is for example such case. You wouldn’t find anything about 1-Legged OAuth in the documentation but the fact is, by now, Jira is still supporting this flow but referring to this wrongly as 2-Legged OAuth. Sadly there aren’t lot of .Net Core libraries which implements OAuth’s 1-Legged, as described in the The OAuth Bible. I implemented this functionality into oauth-dotnetcore library and will show you how this can be used to access Jira APIs.
Once I said that the purpose of simplicity is to hide the complexity and that’s why I love the idea of Amazon IoT Dash Button. But I also like is simplicity of Azure Logic Apps. So how could we connect both worlds?
Feature Flags is useful method to integrate rapidly new functionality, finished or unfinished, into the product. But there are also some traps.
There is good reason to create NuGet packages automated. This will eliminate the difficult and error-prone manual process. Creating and publishing of NuGet packages isn’t hard by the Team Foundation Server (TFS) build, except of prerelease versions.
Last week I evaluated couple of State Machines. It wasn’t some structural evaluation, rather quick overview what is today in the market. I was just about to have something lightweight and easy to use so I have looked into Appccelerate and Stateless from Nicolas Blumhard. As I went through my sample I asked myself: Why we don’t use State Machines frequently? I asked couple of colleagues if they do. They don’t. Do I? No.