New Course Published: Securing Microservices in ASP.NET Core

I’m happy to announce my latest course is available now over at Pluralsight: Securing Microservices in ASP.NET Core.  It offers an in-depth look at various security patterns for microservice architectures.  Here’s what you can expect:

Authentication and authorization are two very important aspects of a secure microservices architecture. In this course, Securing Microservices in ASP.NET Core, you’ll learn how to secure your microservices using a variety of best practice techniques for authentication and authorization. You’ll learn how to work with an identity microservice, how to apply security with and without an API gateway, and how to improve upon the default security approach to reach a best-of-class implementation. By the end of this course you’ll be comfortable implementing best-practice security techniques in microservices architectures.

You can find the course over at Pluralsight.  If you don’t have a Pluralsight account, don’t worry – you can register for a free trial here.

Happy coding!

 Tweet about this on TwitterShare on LinkedInShare on Facebook

One Comment

Attila Takacs

Hello Kevin!

Fist of all thanks for the great courses on pluralsight, specially security! I learned a lot from those courses in the recent time.
I have a question regarding ocelot:
Is it possible to use cookie authentication in ocelot?
architecture: singlespa – angular + ocelot + core apis + idp.
The idea is when you call the ocelot gw from angular or from the browser (an endpoint where authentication is needed) it would redirect you to the idp, there you get a token and based on that a cookie would be created (some claims would be added from a db) and since then this cookie would be used. I guess it is possible to add the cookie to the httpcontext and the angular app would store it and next time the redirection would not happen.
I tried to override the authentication middleware but when i call the challengeAsync on the openidconnect scheme nothing happens, no redirection :( , can you help in this matter?
after a successful challenge on openidconnect i would get the infos from the token and create claims and sign in to cookie scheme.
Do I miss something?

Comments are closed.