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.
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?
My first Smartphone was Symbian based Nokia 3650, followed by dozen Windows Mobile devices like HTC Magician, HTC TyTn and HTC Touch. After Nokia’s great 3650, the iPhone 3G was my second attempt to run on a non Windows Mobile device. Although it was beautiful experience, one must admit, that iOS was at this time really laggy. So I switched again –