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.
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.
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.
Ok, don’t be cross with me, I know the comments aren’t clean code. But sometimes we need them. ReSharper templates is excellent possibility to write your comments quicker and personalized so you can ask the next time: “hey guy what did you meant with this?”.