![Lead Image © Gordon Bussiek, Fotolia.com Lead Image © Gordon Bussiek, Fotolia.com](/var/ezflow_site/storage/images/archive/2024/79/identity-and-access-management-with-authelia/gordon_bussiek_fotolia-bouncer.png/210431-1-eng-US/Gordon_Bussiek_Fotolia-Bouncer.png_medium.png)
Lead Image © Gordon Bussiek, Fotolia.com
Identity and access management with Authelia
Bouncer
To protect a private party from hooligans, you could check the guests' invitations at the entrance yourself, or you could hire a bouncer. Authelia [1] acts as a bouncer for web applications to help you regulate access to services that do not offer their own access controls.
Thanks to Authelia, developers do not have to implement complex and time-consuming user management in their own web applications. Instead, they can deploy Authelia upstream of their own software with two-factor authentication and single sign-on (SSO) by default. In other words, you just need to log in to Authelia to access several authorized applications.
Authelia requires that communication with the web applications be protected by a reverse proxy. The software then connects to this reverse proxy (Figure 1) and checks all incoming requests, just as a bouncer would check invitations.
![](/var/ezflow_site/storage/images/archive/2024/79/identity-and-access-management-with-authelia/figure-1/210435-1-eng-US/Figure-1_large.png)
When you access a web application in a browser, your request is first sent to the reverse proxy, which forwards it directly to Authelia for inspection. When a browser knocks on the door for the first time, it does not have an Authelia session cookie. In this
...Buy this article as PDF
(incl. VAT)