Well, for Many Reasons… While going through the transition from Modular Application to Micro Service Application the authentication methods had changed as well…

while in the old days we would connect our application to Ldap or even a Kerberos Server (and more Active directory a like) in today’s world we are using HTTP based protocols for authentication such as SAML2 and OpenID Connect.

In some cases the overhead of migrating the application to the new way of authentication is a lot of work. in some cases, the application doesn’t have any authentication at all, and you want to make sure users are authenticated before they begin their work.

In the end, we need to take a reverse proxy that will send the authentication request to the OpenID Connect Server and redirect us to the application after we have authenticated.

#kubernetes

Using Httpd As A Reverse Proxy for OpenID Connect Authentication
1.30 GEEK