Hossam Barakat

One of the known limitations of Azure AD B2C is not directly supporting the OAuth 2.0 client credentials grant flow as it is clearly stated in the documentation. The documentation also hint that you can use the OAuth 2.0 client credentials flow because An Azure AD B2C tenant shares some functionality with Azure AD enterprise tenants however there is no details on how to achieve that.

I use Azure DevOps as my build pipelines for a lot of projects, I have faced the following error recently:

Today, I have presented a talk about microservices and Istio service mesh at Sydney Alt.Net User Group.

Building microservices will always lead to a situation where you have certain functionality to be implemented in multiple services. As developers, we try to apply the DRY mantra by building shared libraries which is fine but shared libraries could lead to more complexities depending how we build and share them.

A lot of companies have started the journey of splitting their current monolithic applications into Microservices to gain all the benefits from Microservices such as strong module boundaries, independent deployment, hybrid technologies… which is fine, but what I am concerned about the assumption of splitting monolothic application to microservice will automatically lead to a loosely coupled services.

During the development of microservices we keep our focus on the architecture of each microservice, integration between microservices, defining the boundery for each service,… however we tend to forget about how we are going to monitor those service after deployment to production.

I was working on proof-of-concept to TypeScript with Mocha and I wanted to share my learning.

ASP.NET Core configuration has been re-architected and doesn’t depend on Xml configurations any more, check this excellent article for an introduction about the new configuration system.

When building mobile apps, it’s often required to add authentication to protect the app’s content. Authentication could be through social identity providers like Facebook, Amazon, LinkedIn, etc or through application based credentials. Azure Active Directory Business to Consumer (Azure AD B2C) provides adding identity management functions into application with little coding.

It is known that camelCase is the common convention while working with JavaScript so you will find yourself in an awkward situation when you integrate with WebApi because the default JSON output is formatted using PascalCase.