The past weekend, I went to the Cloudbrew conference. It’s one day of Azure stories from speakers across Europe. I’m sorry, but I’m going to advertise this event because I think they deserve it.
The software I’m working on needs a new authorisation system. The system needs to be prepared for 3 scenarios: to restrict access to a page, to hide part of a page and to block access to data. Let’s solve these problems using claims.
To create a report, I had to combine the contents of several PDFs into one. Thanks to iTextSharp, it’s really easy. Then I had the problem, how do I test this?
Troy Hunt tweeted how a site uses a fake password field so that browsers wouldn’t show the insecure warning. If you want to know the details of this incident, I gladly refer to Troys blog post. In this blog, I want to talk about the deliberate malpractice that goes into this behaviour.