From the course: DevOps Foundations: Microservices

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Service-to-service authentication

Service-to-service authentication - Kubernetes Tutorial

From the course: DevOps Foundations: Microservices

Start my 1-month free trial

Service-to-service authentication

“

- [Instructor] Next, they considered using the same technology as implemented for single sign-on. In the case of Connect Eco, this was OpenID Connect. In this form of authentication, just like all external client requests, all service-to-service traffic would route through the single sign-on gateway. The advantages of this approach are that existing infrastructure can be reused. Additionally, it centralizes all access controls. However, it also means that each microservice must be given its own separate credentials which raises the question, where should these credentials be stored? Additionally, it can be tedious to code the client implementation for some implementations of single sign-on but fortunately for Connect Eco, it is not difficult for OpenID Connect. That said, the Connect Eco team also considered client certificates for their authentication. With this approach, both the client and the server use SSL/TLS to verify their identities. The big advantage of this approach is that…

Contents