These days everywhere I go people seem to talk about wanting to deploy to production more often. It seemed like an endless battle trying to deploy more often as the amount of code to deploy seemed to bulk up in big batches, while we were rambling about buzzwords such as “CI/CD” and “feature toggles“ without …
Implementing Continuous Delivery through Five Steps Read More »
For a long time, I have felt the pain of maintaining relative paths in an application with typescript. You move something and you need to fix the path in 10+ files without easily being able to fix the paths. Also sometimes you see a long import path like “../../../../../../../../../app/config/config.ts“, ugly right? Fear not, typescript path …
In this post I will share a great structure for structuring your Graphql application, using Typescript and Express. The structure consists of these folders/layers (from outer to inner): IOC: Inversion of control provides testability and control over the dependencies in the system. For this, I use “Inversify” Schema: The definition of the GraphQL schemas defined …
How to structure Graphql, Typescript and Express app for scalability Read More »
Now we are getting somewhere, huh!? So far we have played around with the authorization code, hybrid and client credentials flow to get a grasp of when to use what. We have made the authorization server interactive and dynamic by saving user data and IdentityServer data in the database. In this part, we are going …
In this post, we are going to build upon our IdentityServer setup with ASP.NET Core Identity for user management by moving the previously hardcoded IdentityServer configuration data to the database. This enables dynamic change of how IdentityServer is configured instead of needed a rebuild of the server for every configuration change. For this, we are …
Configure IdentityServer with Entity Framework (OIDC Part 6) Read More »
Great that you made it this far! Now we are getting closer to what would be a “normal” scenario. Until now we have played around with authenticating with client credentials, authorization code flow, and hybrid flow – all with hardcoded test users. Of course, this would not work in a production setup, so we will …
OpenID Connect with IdentityServer and ASP.NET Core Identity (OIDC Part 5) Read More »
In the last post we created an authorization code client, enabling the client to get the user claims from the id token, exchanged for the post-login authorization code. That way we were able to display the user roles on an authorized MVC view. This time, instead of getting the user roles from the userInfo endpoint …
OpenID Connect Hybrid Flow for calling resource API (OIDC Part 4) Read More »
OpenID connect authentication with dotnet core and Angular will demonstrate how to set up an app that supports authentication and access control of certain resources in the system. This guide is based on the Identity Server docs which seems to favor a setup with a client, an Identity server and an API being with authorized resources. This …
Creating an OpenID connect system with Angular 8 and IdentityServer4 (OIDC part 1) Read More »