RPJosh
/
authelia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(proxy): clarify the workflow of a client request payload. (#1838) 

Fix #1836
pull/1907/head
Clément Michaud 2021-04-12 23:47:30 +02:00 committed by GitHub
parent ce77aed178
commit 42cee0ed6c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/home/architecture.md
View File

@ -12,7 +12,10 @@ It can be seen as an extension of those proxies providing authentication functio
and a login portal. and a login portal.
As shown in the following architecture diagram, Authelia is directly connected to As shown in the following architecture diagram, Authelia is directly connected to
the reverse proxy but never directly connected to application backends. the reverse proxy but never directly connected to application backends and therefore
the payloads sent by the clients of the protected API will never reach Authelia, only
the authentication pieces will, like the Authorization header for instance. Consequently,
the protected APIs can be a REST, a GraphQL or any other kind of API on top of HTTP.
<p align="center" style="margin:50px"> <p align="center" style="margin:50px">
<img src="../images/archi.png"/> <img src="../images/archi.png"/>